Skip to content

Manual deployment: no CI/CD pipeline

Quick summary

Your deployment is done manually — there is no automated pipeline to build, test, and deploy consistently.

Why this happens

  • No CI/CD pipeline is set up for the project

  • The deployment process is documented but not automated

  • A CI pipeline exists for testing but deployment is still done manually

Minimal example

✗ Broken code
# Manual deployment process:
# 1. SSH into server
# 2. git pull
# 3. npm install
# 4. npm run build
# 5. restart service
# Error-prone, no rollback, no audit trail
✓ Fixed code
# .github/workflows/deploy.yml
on:
  push:
    branches: [main]
jobs:
  deploy:
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npm test
      - run: npm run build
      - run: docker build -t myapp:${{ github.sha }} .
      - run: docker push myapp:${{ github.sha }}
      - run: kubectl set image deployment/app myapp=myapp:${{ github.sha }}

Automating the build, test, and deployment in a CI/CD pipeline ensures consistent, repeatable deployments with an audit trail.

How to diagnose

  • Check if a CI/CD pipeline exists and whether it includes deployment steps

  • Review the deployment process documentation for manual steps

  • Identify which steps are manual and could be automated

How to fix

  • Set up a CI/CD pipeline that builds, tests, and deploys automatically on push or merge

  • Automate the manual deployment steps using scripts or pipeline stages

  • Add deployment gates like approvals or staging promotion for production safety

How to prevent

  • Always set up a CI/CD pipeline for deployment to ensure consistency and reduce human error

  • Use infrastructure as code and pipeline automation for all environment changes

Related Resources

Related Glossary

Related Lessons

  • CI/CD

    Learn about pipelines.

← Back to language