라벨 기반 배포 제어 - GitHub Actions의 혁신적 활용법

개요

전통적 CI/CD의 한계점과 새로운 접근법

전자동 배포의 문제점

# 전통적인 자동 배포 - 모든 PR에 대해 실행
on:
  pull_request:
    branches: [main]
jobs:
  deploy-to-test:
    runs-on: ubuntu-latest
    steps:
      - name: Deploy every PR
        run: echo "Deploying every single PR..." # 비효율적!

수동 배포의 한계

라벨 기반 접근법의 철학

라벨 기반 배포 제어의 핵심 아이디어

라벨의 의미론적 활용

• 이 PR은 검증이 필요한 상태입니다

• 리뷰어는 실제 배포된 환경에서 기능을 확인할 수 있습니다

• QA팀이나 기획자도 즉시 기능을 테스트할 수 있습니다

상태 기반 워크플로우

개발자 경험(DX) 최적화

실전 구현: GitHub Actions와 라벨 연동

기본 워크플로우 구조

name: Label-Based Test Deployment

on:
  pull_request:
    types: [opened, synchronize, reopened, labeled, unlabeled]
    branches: [main]
  workflow_dispatch: # 수동 실행 옵션

permissions:
  contents: read
  packages: write
  pull-requests: write
  issues: write

jobs:
  check-deploy-label:
    runs-on: ubuntu-latest
    outputs:
      should-deploy: ${{ contains(github.event.pull_request.labels.*.name, 'deploy:test') }}
      pr-number: ${{ github.event.number }}
    steps:
      - name: Check for deploy label
        run: |
          echo "Deploy label present: ${{ contains(github.event.pull_request.labels.*.name, 'deploy:test') }}"
          echo "PR Number: ${{ github.event.number }}"

조건부 배포 Job 구현

  deploy-to-test:
    needs: check-deploy-label
    if: needs.check-deploy-label.outputs.should-deploy == 'true'
    runs-on: self-hosted # 또는 ubuntu-latest
    environment: test
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Log in to GitHub Container Registry
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Generate image tag
        id: image-tag
        run: |
          SHORT_SHA=$(echo ${{ github.sha }} | cut -c1-7)
          IMAGE_TAG="test-${SHORT_SHA}"
          echo "tag=${IMAGE_TAG}" >> $GITHUB_OUTPUT

      - name: Build and push Docker image
        uses: docker/build-push-action@v5
        with:
          context: .
          push: true
          tags: ghcr.io/${{ github.repository }}:${{ steps.image-tag.outputs.tag }}
          cache-from: type=gha
          cache-to: type=gha,mode=max

      - name: Deploy to test environment
        run: |
          IMAGE_TAG="${{ steps.image-tag.outputs.tag }}"
          docker compose -f docker-compose.test.yml down
          IMAGE_TAG=$IMAGE_TAG docker compose -f docker-compose.test.yml up -d

      - name: Wait for deployment to be ready
        run: |
          timeout 300 bash -c 'while [[ "$(curl -s -o /dev/null -w ''%{http_code}'' https://test.example.com/health)" != "200" ]]; do sleep 5; done'

라벨 제거 처리

  handle-label-removal:
    if: |
      github.event.action == 'unlabeled' &&
      github.event.label.name == 'deploy:test'
    runs-on: ubuntu-latest
    steps:
      - name: Notify deployment stopped
        uses: actions/github-script@v7
        with:
          script: |
            github.rest.issues.createComment({
              issue_number: context.issue.number,
              owner: context.repo.owner,
              repo: context.repo.repo,
              body: `⏹️ **Test Deployment Stopped**

              The \`deploy:test\` label has been removed.

              **Current Status:** Deployment monitoring disabled
              **Note:** The current deployment will remain active until the next deployment or manual cleanup.

              ---
              *To re-enable test deployment, simply add the \`deploy:test\` label back.*`
            })

스마트한 배포 조건 설정하기

브랜치별 차별화된 배포

  advanced-deploy-check:
    runs-on: ubuntu-latest
    outputs:
      should-deploy: ${{ steps.deploy-decision.outputs.result }}
      deployment-type: ${{ steps.deploy-decision.outputs.type }}
    steps:
      - name: Make deployment decision
        id: deploy-decision
        uses: actions/github-script@v7
        with:
          script: |
            const labels = context.payload.pull_request.labels.map(l => l.name);
            const branchName = context.payload.pull_request.head.ref;
            const hasDeployLabel = labels.includes('deploy:test');

            // 특정 브랜치는 자동 배포
            const autoDeployBranches = ['hotfix/', 'release/'];
            const isAutoDeployBranch = autoDeployBranches.some(prefix =>
              branchName.startsWith(prefix)
            );

            // 복합 조건 평가
            const shouldDeploy = hasDeployLabel || isAutoDeployBranch;
            const deploymentType = isAutoDeployBranch ? 'auto' : 'manual';

            console.log(`Branch: ${branchName}`);
            console.log(`Labels: ${labels.join(', ')}`);
            console.log(`Should deploy: ${shouldDeploy}`);
            console.log(`Deployment type: ${deploymentType}`);

            return {
              result: shouldDeploy,
              type: deploymentType
            };

• hotfix/ 브랜치는 라벨 없이도 자동 배포

• feature/ 브랜치는 라벨이 있을 때만 배포

• docs/ 브랜치는 배포하지 않음

파일 변경사항 기반 조건

  check-file-changes:
    runs-on: ubuntu-latest
    outputs:
      needs-deployment: ${{ steps.changes.outputs.needs-deployment }}
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Check changed files
        id: changes
        run: |
          # 변경된 파일 목록 가져오기
          CHANGED_FILES=$(git diff --name-only ${{ github.event.pull_request.base.sha }}...${{ github.sha }})

          # 배포가 필요한 파일 변경 여부 확인
          DEPLOYMENT_FILES="src/ public/ package.json Dockerfile"
          NEEDS_DEPLOYMENT=false

          for file in $CHANGED_FILES; do
            for pattern in $DEPLOYMENT_FILES; do
              if [[ $file == $pattern* ]]; then
                NEEDS_DEPLOYMENT=true
                break 2
              fi
            done
          done

          # 문서 전용 변경인지 확인
          DOC_ONLY=true
          for file in $CHANGED_FILES; do
            if [[ ! $file == *.md ]] && [[ ! $file == docs/* ]]; then
              DOC_ONLY=false
              break
            fi
          done

          if [[ $DOC_ONLY == true ]]; then
            NEEDS_DEPLOYMENT=false
          fi

          echo "needs-deployment=$NEEDS_DEPLOYMENT" >> $GITHUB_OUTPUT
          echo "Changed files: $CHANGED_FILES"
          echo "Needs deployment: $NEEDS_DEPLOYMENT"

시간 기반 배포 제한

  check-deployment-time:
    runs-on: ubuntu-latest
    outputs:
      is-allowed-time: ${{ steps.time-check.outputs.allowed }}
    steps:
      - name: Check deployment time window
        id: time-check
        run: |
          # UTC 기준 시간 확인 (한국시간 09:00-18:00 = UTC 00:00-09:00)
          CURRENT_HOUR=$(date -u +%H)
          ALLOWED=false

          # 평일 낮 시간대만 배포 허용
          DAY_OF_WEEK=$(date +%u) # 1=월요일, 7=일요일

          if [[ $DAY_OF_WEEK -le 5 ]] && [[ $CURRENT_HOUR -ge 0 ]] && [[ $CURRENT_HOUR -le 9 ]]; then
            ALLOWED=true
          fi

          echo "allowed=$ALLOWED" >> $GITHUB_OUTPUT
          echo "Current hour (UTC): $CURRENT_HOUR"
          echo "Day of week: $DAY_OF_WEEK"
          echo "Deployment allowed: $ALLOWED"

자동화된 피드백 시스템 구축

단계별 상태 피드백

  provide-feedback:
    needs: [check-deploy-label, deploy-to-test]
    if: always()
    runs-on: ubuntu-latest
    steps:
      - name: Update deployment status
        uses: actions/github-script@v7
        with:
          script: |
            const { needs } = context.payload.action || {};
            const shouldDeploy = '${{ needs.check-deploy-label.outputs.should-deploy }}' === 'true';
            const deployResult = '${{ needs.deploy-to-test.result }}';
            const prNumber = ${{ github.event.number }};

            let status = '';
            let emoji = '';
            let color = '';

            if (!shouldDeploy) {
              status = 'No deployment requested';
              emoji = 'ℹ️';
              color = 'gray';
            } else if (deployResult === 'success') {
              status = 'Deployment successful';
              emoji = '✅';
              color = 'green';
            } else if (deployResult === 'failure') {
              status = 'Deployment failed';
              emoji = '❌';
              color = 'red';
            } else {
              status = 'Deployment in progress';
              emoji = '🚀';
              color = 'yellow';
            }

            const deploymentUrl = 'https://test-pr-' + prNumber + '.example.com';
            const workflowUrl = `${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}`;

            let commentBody = `${emoji} **Test Deployment Status: ${status}**\n\n`;

            if (shouldDeploy && deployResult === 'success') {
              commentBody += `🔗 **Test URL:** [${deploymentUrl}](${deploymentUrl})
📦 **Image Tag:** test-${process.env.GITHUB_SHA.substring(0, 7)}
⏰ **Deployed at:** ${new Date().toISOString()}
🌿 **Branch:** \`${{ github.head_ref }}\`

---
**Quick Actions:**
- 🔄 Remove \`deploy:test\` label to stop deployment monitoring
- 📋 [View detailed logs](${workflowUrl})
- 🐛 Found an issue? Comment below to discuss`;
            } else if (shouldDeploy && deployResult === 'failure') {
              commentBody += `❌ The deployment to test environment failed.

**Troubleshooting Steps:**
1. 📋 [Check the detailed logs](${workflowUrl})
2. 🔧 Verify your code builds locally: \`npm run build\`
3. 🔍 Check for any breaking changes or missing dependencies
4. 🔄 Push fixes and the deployment will automatically retry

**Need Help?**
- Comment \`@devops-team\` for assistance
- Check our [deployment troubleshooting guide](link-to-docs)`;
            } else if (!shouldDeploy) {
              commentBody += `This PR currently has no deployment requested.

**To deploy to test environment:**
1. Add the \`deploy:test\` label to this PR
2. Deployment will start automatically
3. You'll receive a notification when it's ready

*Deployment typically takes 2-3 minutes to complete.*`;
            }

            // 기존 배포 상태 댓글 찾기 및 업데이트
            const { data: comments } = await github.rest.issues.listComments({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: prNumber
            });

            const botComment = comments.find(comment =>
              comment.user.login === 'github-actions[bot]' &&
              comment.body.includes('**Test Deployment Status:')
            );

            if (botComment) {
              await github.rest.issues.updateComment({
                owner: context.repo.owner,
                repo: context.repo.repo,
                comment_id: botComment.id,
                body: commentBody
              });
            } else {
              await github.rest.issues.createComment({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: prNumber,
                body: commentBody
              });
            }

동적 라벨 관리

  manage-status-labels:
    needs: [deploy-to-test]
    if: always()
    runs-on: ubuntu-latest
    steps:
      - name: Update status labels
        uses: actions/github-script@v7
        with:
          script: |
            const prNumber = ${{ github.event.number }};
            const deployResult = '${{ needs.deploy-to-test.result }}';

            // 기존 상태 라벨들 제거
            const statusLabels = ['deployment:success', 'deployment:failed', 'deployment:in-progress'];

            for (const label of statusLabels) {
              try {
                await github.rest.issues.removeLabel({
                  owner: context.repo.owner,
                  repo: context.repo.repo,
                  issue_number: prNumber,
                  name: label
                });
              } catch (error) {
                // 라벨이 없으면 무시
              }
            }

            // 새로운 상태 라벨 추가
            if (deployResult === 'success') {
              await github.rest.issues.addLabels({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: prNumber,
                labels: ['deployment:success']
              });
            } else if (deployResult === 'failure') {
              await github.rest.issues.addLabels({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: prNumber,
                labels: ['deployment:failed']
              });
            }

통합 알림 시스템

  notify-external:
    needs: [deploy-to-test]
    if: needs.deploy-to-test.result == 'success'
    runs-on: ubuntu-latest
    steps:
      - name: Notify Slack
        uses: 8398a7/action-slack@v3
        with:
          status: custom
          custom_payload: |
            {
              "text": "🚀 Test deployment completed",
              "attachments": [
                {
                  "color": "good",
                  "fields": [
                    {
                      "title": "PR",
                      "value": "<${{ github.event.pull_request.html_url }}|#${{ github.event.number }} - ${{ github.event.pull_request.title }}>",
                      "short": false
                    },
                    {
                      "title": "Test URL",
                      "value": "https://test-pr-${{ github.event.number }}.example.com",
                      "short": true
                    },
                    {
                      "title": "Author",
                      "value": "${{ github.event.pull_request.user.login }}",
                      "short": true
                    }
                  ]
                }
              ]
            }
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

성과 측정과 최적화

핵심 성과 지표(KPI)

• 전체 배포 수 60% 감소 (월 45회 → 18회)

• 의미 있는 배포 비율 90% 향상 (40% → 95%)

• 배포 관련 GitHub Actions 실행 시간 40% 절약

• 테스트 서버 CPU 사용률 30% 감소

• 불필요한 Docker 이미지 생성 65% 감소

• GitHub Actions 실행 비용 40% 절약

지속적 개선 전략

name: Auto-cleanup stale deployments

on:
  schedule:
    - cron: '0 2 * * *' # 매일 02:00 UTC

jobs:
  cleanup-stale-deployments:
    runs-on: ubuntu-latest
    steps:
      - name: Find stale deployments
        uses: actions/github-script@v7
        with:
          script: |
            const { data: pulls } = await github.rest.pulls.list({
              owner: context.repo.owner,
              repo: context.repo.repo,
              state: 'open'
            });

            for (const pr of pulls) {
              const deployLabel = pr.labels.find(l => l.name === 'deploy:test');
              if (!deployLabel) continue;

              // 라벨이 추가된 지 7일 이상 경과했는지 확인
              const labelAge = Date.now() - new Date(deployLabel.created_at).getTime();
              const sevenDays = 7 * 24 * 60 * 60 * 1000;

              if (labelAge > sevenDays) {
                await github.rest.issues.removeLabel({
                  owner: context.repo.owner,
                  repo: context.repo.repo,
                  issue_number: pr.number,
                  name: 'deploy:test'
                });

                await github.rest.issues.createComment({
                  owner: context.repo.owner,
                  repo: context.repo.repo,
                  issue_number: pr.number,
                  body: `🧹 **Auto-cleanup Notice**

                  The \`deploy:test\` label has been automatically removed as this deployment has been active for over 7 days.

                  If you still need the test deployment, simply re-add the label.`
                });
              }
            }

다음 단계: 멀티 환경 배포로의 발전

다음 단계의 목표들

마이그레이션 전략

마무리

• 📉 불필요한 배포 60% 감소

• ⚡ 배포 요청 시간 50% 단축

• 💰 인프라 비용 40% 절약

• 😊 개발자 만족도 크게 향상

• 작은 규모부터 시작해서 점진적으로 확장하세요

• 팀의 피드백을 적극 수렴하여 지속적으로 개선하세요

• 자동화된 모니터링을 통해 시스템의 건강성을 확인하세요

• 문서화를 통해 팀 전체가 시스템을 이해할 수 있도록 하세요

• GitHub Actions 워크플로우 트리거

• GitHub Script Action 사용법

• Pull Request 라벨 관리 API

• GitHub Actions 조건부 실행

• 워크플로우 보안 가이드