CI/CD Pipeline

CI/CD Pipeline

Project: Drop{{PROJECT_NAME}} Version: 0.1.0{{VERSION}} Date: 2026-02-23{{DATE}} Author: Platform Architect (AI){{AUTHOR}} Status: Draft | In Review | Approved Reviewers: Alem Bašić (CEO){{REVIEWERS}}

Document History

1. Overview

Drop uses GitHub Actions for CI with a 5-job pipeline covering lint, typecheck, unit tests, E2E tests, and Docker build. The CD (automated deployment) pipeline to AWS App Runner is tracked as a pending item — currently CI builds but does not deploy automatically. Staging deployment is manual via fly deploy to Fly.io (Stockholm).

CI/CD Platform: GitHub{{PLATFORM}} Actions (.github/workflows/ci.yml) Container Registry: AWS{{REGISTRY}} ECR (324480209768.dkr.ecr.eu-west-1.amazonaws.com/drop-web) Deployment Target (production):Target: AWS{{DEPLOY_TARGET}} App Runner (eu-west-1) Deployment Target (staging): Fly.io (Stockholm, region arn) Strategy: Rolling{{STRATEGY}} (App Runner managed)

2. Pipeline Overview

flowchart LR
    subgraph Source
        PR[Pull Request\nto main/master]Request]
        MERGE[PushMerge to\nmain/master]to main]
    end

    subgraph CI [CI["CI — runs on every push/PR"]
        LINT[1.Lint lint-and-typecheck\nnpm& runFormat]
        lint\ntscTEST_UNIT[Unit --noEmit]Tests]
        TEST[2.TEST_INT[Integration test\nvitestTests]
        run]SAST[SAST Scan]
        SCA[Dependency Scan]
        BUILD[3.Build build\nnext build]
        E2E[4. e2e\nPlaywright\nuser-flows + full-flows]
        DOCKER[5. docker-build\ndocker build -t drop-app:ci]Artifact]
    end

    subgraph CD_STG [CD_DEV["CD Staging — manual"Dev Auto-Deploy"]
        STG[flyDEPLOY_DEV[Deploy deploy\nFly.ioto Stockholm]Dev]
        SMOKE_DEV[Smoke Tests]
    end

    subgraph CD_PROD [CD_STAGING["CD Production— Staging (auto on main)"]
        DEPLOY_STG[Deploy to Staging]
        TEST_E2E[E2E Tests]
        PERF[Performance Tests]
    end

    subgraph CD_PROD["CD — pendingProduction implementation"(manual gate)"]
        APPROVAL[Manual Approval\nviaApproval]
        GitHubDEPLOY_PROD[Deploy Environments]to PROD[awsProduction]
        apprunner\nstart-deployment]SMOKE_PROD[Smoke Tests]
        MONITOR[Verify Monitoring]
    end

    PR --> LINT
    MERGE --> LINT
    LINT --> TESTTEST_UNIT
    LINTTEST_UNIT --> TEST_INT
    TEST_INT --> SAST
    SAST --> SCA
    SCA --> BUILD
    TESTMERGE --> E2ECD_DEV
    BUILD --> E2EDEPLOY_DEV
    E2EDEPLOY_DEV --> DOCKERSMOKE_DEV
    DOCKERSMOKE_DEV --> STGDEPLOY_STG
    DOCKERDEPLOY_STG --> TEST_E2E
    TEST_E2E --> PERF
    PERF --> APPROVAL
    APPROVAL --> PRODDEPLOY_PROD
    DEPLOY_PROD --> SMOKE_PROD
    SMOKE_PROD --> MONITOR

3. Source Control Configuration

3.1 Branching Strategy

Strategy: GitHub{{BRANCH_STRATEGY}} Flow (feature branches off main, PR into main)

3.2 Branch Protection Rules

Protected Branches: main, develop

3.3 Code Review Requirements

• Minimum 1{{APPROVALS}} approvalapproval(s) required before merge
• At least one approval from Alema Bašićcode owner (orsee delegated lead)CODEOWNERS)
• All review comments must be resolved before merge
• Review turnaround SLA: 24{{REVIEW_SLA}} business hours
• Auto-assign reviewers via: {{ASSIGN_MECHANISM}}

4. Build Stage

4.1 Build Tool & Configuration

Multi-stage build:

Stage 1: deps     — npm ci + native dependencies
Stage 2: builder  — npm run build (Next.js standalone)
Stage 3: runner   — minimal image, copies only public/ + .next/standalone/ + .next/static/

4.2 Dependency Caching

4.3 Artifact Generation

5. Test Stages

5.1 Unit Tests

5.2 Integration Tests

5.3 E2E Tests

5.4 Security Scanning

Note: Security scanning tracked in security/hardening-checklist.md. npm audit and Snyk integration are pending.

5.5 Linting & Formatting

6. Deploy Stages

6.1 Deployment Strategy

Strategy: Rolling{{DEPLOY_STRATEGY}} (App Runner managed)

App Runner handles deployment atomically — new container version deployed, health checks verified, traffic shifted. No blue-green or canary at this stage.

App RunnerRolling Deployment:

• Trigger:Batch awssize: apprunner{{BATCH_SIZE}}% start-deploymentof (currentlyinstances
manual)
• Pause between batches: {{PAUSE}}min
• Health check:check GETwait: /api/health every 30s{{HEALTH_WAIT}}s
• Auto-rollback:Rollback App Runner reverts if new deployment failstrigger: health checks
check
• Deployment time: ~3-5 minutesfailure

StagingCanary Deployment (Fly.io)if Deployment:used):

• Command:Initial flycanary deployweight: (manual){{CANARY_INITIAL}}%
• Region:Increment: arn{{CANARY_INCREMENT}}% (Stockholm)every {{CANARY_INTERVAL}}min
• Auto-scale:Promotion Scalescriteria: toerror 0rate when< idle,{{ERROR_THRESHOLD}}%, auto-startsp99 < {{LATENCY_THRESHOLD}}ms
• Rollback trigger: automatic on requestthreshold breach

6.2 Environment Promotion

PR Branch → CIDev (auto) → Staging (manualauto flyon deploy)main merge) → Production (manual apprunner start-deployment)approval)

6.3 Approval Gates

Production Approval Required: Yes (manual) Approvers: Alem Bašić{{PROD_APPROVERS}} (soleat approverleast during{{APPROVAL_COUNT}} MVP phase)required) Approval Window: No automated timeout{{APPROVAL_WINDOW}}h (manualpipeline process)cancels after timeout) Emergency Override: Direct{{EMERGENCY_OVERRIDE}} aws apprunner start-deployment via AWS Console (Alem only)

6.4 Feature Flags Integration

Feature Flag Tool: Environment{{FF_TOOL}} variables (build-timeFlag via Next.js NEXT_PUBLIC_FF_* pattern)

# Rollback via AWS CLI (revert to previous ECR image)
aws apprunner start-deployment \
  --service-arn arn:aws:apprunner:eu-west-1:324480209768:service/drop-web/8e45b0d335304487a1880f4e32d6aeec \
  --region eu-west-1