Your releases lose time to manual steps, team handoffs, email approvals, flaky tests, test environments, tribal knowledge or release windows.manual steps.

Jenkinsfile

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { sh 'make build' }
    }
    stage('Tests') {
      parallel {
        stage('Unit tests') {
          steps { sh 'make test' }
        }
        stage('Security scan') {
          steps { sh 'make scan' }
        }
      }
    }
    stage('Deploy to staging') {
      steps { sh './deploy.sh staging' }
    }
    stage('Approval') {
      steps {
        input message: 'Go to production?',
              submitter: 'change-board'
      }
    }
    stage('Deploy to production') {
      steps { sh './deploy.sh production' }
    }
  }
  post { always { sh './change-record.sh' } }
}

.github/workflows/release.yml

name: release
on:
  push:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: make build test scan

  staging:
    needs: build
    runs-on: ubuntu-latest
    environment: staging
    steps:
      - uses: actions/checkout@v4
      - run: ./deploy.sh staging

  production:
    needs: staging
    runs-on: ubuntu-latest
    # required reviewers: change board
    environment: production
    steps:
      - uses: actions/checkout@v4
      - run: ./deploy.sh production
      - run: ./change-record.sh

environments.tf

# One module for staging and production,
# so staging mirrors production.

module "staging" {
  source        = "./modules/service"
  name          = "checkout-service"
  environment   = "staging"
  instance_type = "t3.medium"
  min_size      = 2
}

module "production" {
  source        = "./modules/service"
  name          = "checkout-service"
  environment   = "production"
  instance_type = "t3.medium"
  min_size      = 4
}