CI/CD
also: continuous integration, continuous deployment, continuous delivery, ci pipeline
An automatic system that checks every code change, usually by building the app and running its tests, and can then release it to users if everything passes.
Continuous integration (CI) automatically builds and tests every change pushed to a shared repository. Continuous delivery or deployment (CD) automatically prepares or ships passing changes to staging or production. Common tools include GitHub Actions and GitLab CI.
A factory line with inspection stations. Every part is measured and tested automatically. Anything that fails is pulled before it ships, without anyone having to remember to check.
CI catches problems your agent missed, on every change, even when you forget to ask for tests. When an agent says "CI is failing," an automatic check rejected the change, and that's worth understanding before merging.
CI is failing on the lint step, not the tests. I'll fix the two lint errors and push again so the pipeline is green before we merge.
The CI/CD pipeline failed after my last push. Read the failing job's logs, tell me which step failed and why, and fix the cause rather than disabling the check.
Thinking a green CI run means the app is correct. CI only runs the checks it's set up to run. If a feature has no tests, CI can pass while that feature is broken.