Development
CI/CD
Also known as: Continuous Integration, Continuous Deployment, Continuous Delivery
An automated pipeline where committing code triggers an automatic build, test, and deployment — Continuous Integration / Continuous Deployment.
CI/CD stands for Continuous Integration and Continuous Deployment (or Delivery) — the practice of automating the path from a code change to a live, deployed update. Instead of a person manually building and uploading the site, the pipeline does it: a commit is pushed, the system builds the project, runs whatever checks are configured, and deploys the result.
Continuous Integration is the first half: changes are merged and built frequently, so problems surface immediately rather than piling up. Continuous Deployment is the second: once a build passes, it ships automatically. The commit is the trigger; the deploy is the consequence.
The payoff is speed with safety. Updates go out the moment they are ready, every deploy is consistent and repeatable, and because each deployment is a discrete, recorded step, a regression can be rolled back cleanly. It is the difference between "saving the code is deploying it" and a manual, error-prone release process.