Building a Windows Client Deployment Pipeline with TeamCity

Oliveyoung's POS and self-checkout team built a TeamCity-based CI/CD pipeline to resolve human error and environment dependency issues arising from the existing manual-centric deployment process.

Previously, developers had to go through a cumbersome process of directly building files, selecting and uploading them to S3, and manually editing version files. This structure had inherent limitations: results could vary depending on the developer's PC environment, and it was difficult to command a batch update across more than 3,000 terminals.

To improve this, automation was carried out in the following stages.

• Setting CI/CD boundaries: Designing the process to fit the structure where the client is the subject of updates
• Process modularization: Breaking down the entire process into small steps of about 1-5 lines each to ensure testability
• Building a dedicated build agent: Allocating a separate EC2 resource for C# builds and installing essential tools such as nuget, msbuild, and jq
• Implementing automation flow: Configuring TeamCity to pull the source, build it, and then automatically transfer files to S3 via AWS CLI

As a result, they minimized manual developer intervention and established a stable deployment environment where the client autonomously downloads the latest version from S3.