METHODOLOGY

CI/CD

Continuous Integration / Continuous Delivery

Every code change is automatically built, tested, and prepared for release. Some teams take it one step further and ship to production on every green build.

Last reviewed: 2026-05-24 byKevin Riedl wiki β†—

Continuous Integration means the team’s code is merged and built on every change, not in a big-bang integration at the end. Continuous Delivery means every successful build is one button-press away from production. Continuous Deployment removes the button: every green build ships, automatically.

Most teams do CI well, CD intermittently, and Continuous Deployment almost never. The bottleneck is rarely the tooling. It is the trust in the test suite and the team’s willingness to fix a broken build inside an hour. Without those, automated deploys just ship bugs faster.

Wavect ships every project with CI configured from day one. CD configuration depends on whether the project has the test coverage and the operational discipline to make it safe. We will tell you which one you have.

// FAQ

FAQs

FAQs

CI: every change is built and tested on merge. CD (Continuous Delivery): every green build is one button-press from production. Continuous Deployment: every green build ships automatically, no button. They are a maturity ladder, not synonyms.
Because CD requires confidence in the test suite that most teams do not have. Without good coverage and fast rollback, automated deploys just ship bugs faster. CI is mostly tooling; CD is mostly discipline.
Under 10 minutes for the inner loop (build, unit, lint), under 30 minutes including integration tests. Slower than that and engineers stop running it locally and start merging on hope. Pipeline speed is a leverage metric: invest in it.