CI/CD · Ship safely, repeatedly

What are common CI/CD mistakes?

Easyanti-patternsci/cdreliabilityUpdated Oct 2026
Quiz this track

Short answer

Common mistakes include slow or flaky pipelines, secrets in logs, rebuilding per environment, snowflake environments, missing rollback, manual steps, and treating a green pipeline as proof of production health.

Most pipeline problems are process problems expressed in YAML. The pipeline becomes a place where hidden manual knowledge, inconsistent environments and untested recovery paths accumulate.

  • A merge-blocking suite so slow that people batch changes or bypass it
  • Flaky tests normalized with retries until failures lose meaning
  • Secrets echoed in logs or available to untrusted pull request jobs
  • Rebuilding the artifact separately for each environment
  • Environments configured by hand and drifting from code
  • No tested rollback path and no way to disable a bad feature quickly
  • Production deployment with no post-deploy verification
  • Pipeline changes merged without review
yaml
deploy:
  script:
    - echo $DEPLOY_TOKEN
    - ./deploy.sh production
Echoing a credential and deploying without verification are both avoidable failures.
A green pipeline means the checks passed. It does not mean users are healthy, migrations are safe or the rollback works. Those require verification and rehearsal.

Follow-ups you should expect

Interviewers use these to check whether the first answer was understanding or memorisation.

  1. 1Which mistake causes the most long-term damage?
  2. 2How do you recover trust in a flaky pipeline?
  3. 3Why is rebuilding per environment dangerous?
  4. 4What would you fix first in a neglected pipeline?

Say it in the interview

The most common mistakes are slow or flaky feedback, secrets leaking into logs or untrusted jobs, rebuilding artifacts per environment, hand-built environments, and no tested rollback. I also see teams treat a green pipeline as proof that production is healthy. If I inherited a neglected pipeline, I would first make the merge path fast and trustworthy, then fix secret handling and add a rehearsed rollback before increasing deployment frequency.

Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.

Related questions

Reading is step one

Now say it out loud.

Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live CI/CD mock interview and get scored feedback on depth, clarity and confidence.