CI/CD stands for Continuous Integration and Continuous Deployment, two practices that automate building, testing, and releasing software. Continuous Integration means regularly merging code into a shared repository and running automated tests to catch issues early. Continuous Deployment takes this further by automatically releasing changes to production after they pass tests. CI/CD pipelines are executed by automation tools and often involve multiple steps including linting, compiling, testing, packaging, and deployment.
Why it matters
CI/CD shortens development cycles, reduces human error, and ensures that your web application or backend stays in a stable state. It encourages teams to integrate their work frequently, improving visibility and collaboration. Automated pipelines also allow you to deploy with confidence rather than relying on manual steps.
Examples
GitHub Actions, GitLab CI, and CircleCI are popular tools for implementing CI/CD. Many lessons reference CI/CD concepts, such as Build and Test Pipelines and Deployment Pipelines.