Belajar Git Branching Strategies - CI/CD Integration dengan Branching Strategy

#Pendahuluan

Setelah di episode 16 kita mempelajari Branch Protection & Rulesets — bagaimana mengamankan branch utama — pada episode ini kita membahas bagaimana CI/CD pipeline terintegrasi dengan branching strategy. Pipeline yang berbeda untuk branch yang berbeda mengoptimalkan waktu dan resource.

Tidak semua branch membutuhkan test suite yang sama: feature branch cukup lint + unit test, sementara main membutuhkan full test + staging deployment.

#Pipeline Trigger Berdasarkan Branch

#Feature Branch (feature/*)

on:
  push:
    branches: ['feature/**']
jobs:
  lint:
    runs-on: ubuntu-latest
    steps: [npm run lint]
  unit-test:
    runs-on: ubuntu-latest
    steps: [npm test -- --unit]

Cukup lint dan unit test — cepat dan murah. Feedback untuk developer dalam hitungan menit.

#Develop Branch

on:
  push:
    branches: ['develop']
jobs:
  integration-test:
    runs-on: ubuntu-latest
    steps: [npm test -- --integration]
  e2e-test:
    runs-on: ubuntu-latest
    steps: [npm run test:e2e]

Integration test dan E2E test berjalan — lebih lama tetapi memastikan kode stabil.

#Main / Release Branch

on:
  push:
    branches: ['main', 'release/**']
jobs:
  full-test:
    runs-on: ubuntu-latest
    steps: [npm test]
  build:
    runs-on: ubuntu-latest
    steps: [npm run build]
  deploy-staging:
    needs: [full-test, build]
    steps: [./deploy.sh staging]

Full test suite + build + deploy ke staging. Production deploy membutuhkan approval manual.

#Hotfix Branch (hotfix/*)

on:
  push:
    branches: ['hotfix/**']
jobs:
  full-test:
    runs-on: ubuntu-latest
    steps: [npm test]
  deploy-production:
    needs: [full-test]
    steps: [./deploy.sh production]

Hotfix melewati staging → langsung ke production (setelah approval).

#Environment Deployment Strategy

#Branch to Environment Mapping

#Manual Approval Gate

Production deploy selalu membutuhkan approval manual. Ini bisa dikonfigurasi di GitHub Actions:

deploy-production:
  needs: [deploy-staging]
  environment:
    name: production
  runs-on: ubuntu-latest
  steps:
    - run: ./deploy.sh production

GitHub akan menampilkan tombol "Approve" yang harus diklik sebelum deploy berjalan.

#Canary & Blue-Green Deployment via Branching

#Canary Deployment

Deploy ke sebagian kecil user terlebih dahulu:

Canary deployment menggunakan branch atau tag untuk menandai versi canary.

#Blue-Green Deployment

Dua environment identik — blue (production saat ini) dan green (versi baru):

# Deploy ke green
./deploy.sh green
 
# Switch traffic dari blue ke green
./switch-traffic.sh green
 
# Rollback jika ada masalah
./switch-traffic.sh blue

Branch blue dan green bisa digunakan untuk menandai versi di setiap environment.

#Penutup

Pada episode 17 ini, kalian telah memahami CI/CD Integration:

• Pipeline trigger berbeda berdasarkan branch: feature (lint + unit), develop (integration), main (full + staging), hotfix (production path).
• Environment mapping: feature ke dev, develop ke development, main ke staging, tag ke production.
• Manual approval gate untuk production deploy — mengurangi risiko deploy berisiko.
• Canary deployment: deploy 1% user terlebih dahulu, monitor, full rollout.
• Blue-green deployment: dua environment, switch traffic.

Di episode 18 selanjutnya kita akan mempelajari Monorepo Branching Strategy — tantangan branch yang sama mempengaruhi banyak package, path-based filtering di CI, dan CODEOWNERS per package. Sampai jumpa di episode 18!