Pipeline Design — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— CI/CD Pipeline Design
📋Stages
⚙️Sharding
🔄Gates
✅Smoke Test
🎯 Next: Test →
Step 1 / 4
Speed
Pipeline Stages
lint → test → build → deploy-staging: each stage gates the next💡 Analogy
Like airport security: document check (lint) → security scan (test) → gate boarding (build) → flight (deploy).
Pipeline stages run in sequence with gates. Fast checks (lint) run first. Expensive checks (tests) run in parallel. Only successful stages unlock the next.
Console Output
> lint: 62s ✅
> test (4 shards): 90s (parallel) ✅
> build: 45s (after test) ✅
> Total: ~3min (vs 10min sequential)
●pipeline.yml
Pipeline StagesL1–8
1# Optimized CI/CD pipeline: lint → test → build → deploy
2name: Production Pipeline
3on:
4  push:
5    branches: [main]
6 
7jobs:
8  # Stage 1: Fast lint/typecheck in parallel
9  lint:
10    runs-on: ubuntu-latest
11    steps:
12      - uses: actions/checkout@v4
13      - run: npm ci
14      - run: npm run lint && npm run typecheck
15 
16  # Stage 2: Tests with sharding (4× faster)
17  test:
18    runs-on: ubuntu-latest
19    strategy:
20      matrix:
21        shard: [1, 2, 3, 4]        # 4 parallel test runners
22    steps:
23      - uses: actions/checkout@v4
24      - run: npm ci
25      - run: npx jest --shard=${{ matrix.shard }}/4  # each shard runs 25%
26 
27  # Stage 3: Build only after all tests pass
28  build:
29    needs: [lint, test]             # blocks until ALL matrix shards pass
30    runs-on: ubuntu-latest
31    steps:
32      - uses: actions/checkout@v4
33      - uses: docker/build-push-action@v5
34        with:
35          tags: myapp:${{ github.sha }}
36          cache-from: type=gha
37 
38  # Stage 4: Deploy to staging, run smoke tests
39  deploy-staging:
40    needs: [build]
41    runs-on: ubuntu-latest
42    environment: staging
43    steps:
44      - run: kubectl set image deployment/myapp myapp=myapp:${{ github.sha }}
45      - run: sleep 30 && curl -f https://staging.myapp.com/health
45 lines
Timeline — 4 Steps
Pipeline Stages
lint → test → build → deploy-staging: each stage gates the next💡 Analogy
Like airport security: document check (lint) → security scan (test) → gate boarding (build) → flight (deploy).
Pipeline stages run in sequence with gates. Fast checks (lint) run first. Expensive checks (tests) run in parallel. Only successful stages unlock the next.
Console Output
> lint: 62s ✅
> test (4 shards): 90s (parallel) ✅
> build: 45s (after test) ✅
> Total: ~3min (vs 10min sequential)

Was this page helpful?

Discussion

lint → test → build → deploy-staging: each stage gates the next

💡 Analogy

Like airport security: document check (lint) → security scan (test) → gate boarding (build) → flight (deploy).

Pipeline stages run in sequence with gates. Fast checks (lint) run first. Expensive checks (tests) run in parallel. Only successful stages unlock the next.

Console Output

> lint: 62s ✅
> test (4 shards): 90s (parallel) ✅
> build: 45s (after test) ✅
> Total: ~3min (vs 10min sequential)

lint → test → build → deploy-staging: each stage gates the next

💡 Analogy

Like airport security: document check (lint) → security scan (test) → gate boarding (build) → flight (deploy).

Pipeline stages run in sequence with gates. Fast checks (lint) run first. Expensive checks (tests) run in parallel. Only successful stages unlock the next.

Console Output

> lint: 62s ✅
> test (4 shards): 90s (parallel) ✅
> build: 45s (after test) ✅
> Total: ~3min (vs 10min sequential)