GuidesDevOps
CI/CD: deploy on every push, without stress
The pipeline
- 1PushCode lands on the main branch.
- 2TestsAutomatic checks: types, tests, links.
- 3BuildThe site or app is built.
- 4DeployReleased, then checked.
What it changes
Without CI/CD
With CI/CD
Good practices
- A working branch, then a merge: only the main branch deploys.
- Secrets (keys, passwords) in the service’s vault, never in the code.
- A rollback ready before you need it.
Further reading: Hosting on a VPS, staging and Docker.
Frequently asked questions
- CI and CD, what is the difference?
- CI (continuous integration) tests and builds every change. CD (continuous deployment) automatically releases what passed CI.
- Which tools?
- GitHub Actions, GitLab CI or an equivalent. For a small project, your repository host’s service is enough.
- What if a release breaks something?
- Roll back to the previous version in one command. Small releases make the cause easy to find.