# CI/CD

Concept · [Technical basics](https://ecosystem.samcarlton.com/technical)

Also called: CI, CI CD, continuous integration, continuous delivery, continuous deployment, CI pipeline, build pipeline, deploy pipeline

Continuous integration and continuous delivery: automation that runs the tests on every change pushed to the [repository](https://ecosystem.samcarlton.com/repository) and, when they pass, prepares or ships the new version without manual steps.

**For example:** Every [pull request](https://ecosystem.samcarlton.com/pull-request) runs the CI/CD [pipeline](https://ecosystem.samcarlton.com/sales-funnel). A failing test blocks the merge, and a passing merge [deploys](https://ecosystem.samcarlton.com/deployment) to the [live site](https://ecosystem.samcarlton.com/production) within minutes.

## Connects to (7)

- [Automated check](https://ecosystem.samcarlton.com/automated-check): A test or rule a computer runs to catch problems without a person looking, such as tests, type checkers and style checkers.
- [Testing](https://ecosystem.samcarlton.com/testing): Checking that software does what it should, before your users find the problems for you.
- [Deployment](https://ecosystem.samcarlton.com/deployment): Putting the latest version of your app onto the live servers where real users can reach it.
- [GitHub Actions](https://ecosystem.samcarlton.com/github-actions): GitHub's service for running automatic jobs when code changes, such as running tests and deploying the app.
- [Pull request](https://ecosystem.samcarlton.com/pull-request): A request to merge the changes on one branch into the main code.
- [DevOps](https://ecosystem.samcarlton.com/devops): The practice, and job, of combining software development with running it in production: automating builds, tests and deployments and…
- [GitLab](https://ecosystem.samcarlton.com/gitlab): A platform for hosting code repositories, reviewing changes and running automatic builds.

Map view: https://ecosystem.samcarlton.com/ci-cd