Implementing Multi-Region Deployment and Automation with GitHub Actions at Kakao Webtoon

A Kakao Webtoon frontend developer shared their experience building a CI/CD pipeline using GitHub Actions. The key points are as follows:

1. Test and Notification Automation: Upon push events, Node.js tests (lint, tsc, build) are executed in a Linux environment, skipping unnecessary npm install via node_modules caching. On failure or success, notifications are sent to Slack via a custom Composite Action.

2. Multi-Region Deployment: To accommodate the characteristics of a global service, a branch naming convention in the format deploy/[region]/[env]/[name] was applied. The region (kor, twn, tha) and environment (qa, sandbox, real) are extracted from the branch name to load the corresponding AWS configuration values (Secrets) and perform the appropriate build and deployment.

3. Scheduled Deployment: Using the schedule event, deployments are automatically executed at 9 AM on weekdays. By leveraging actions/cache to compare commit SHAs, the deployment steps are optimized to run only when changes are detected.

4. GitHub CLI Integration: Recently, the deployment process was improved by using GitHub CLI to trigger workflows and pass required information (region, env) as arguments, instead of pushing branches.