CI/CD stands for Continuous Integration (CI) and Continuous Deployment or Continuous Delivery (CD). Continuous Integration encompasses the automated testing and merging of new code with existing software, with development teams using automation tools (e.g. CircleCI, Jenkins) to automatically test and merge new code as seamlessly as possible. Continuous Delivery, on the other hand, is a natural follow-up to CI. Instead of preparing one big release a few times in the year, a new code is available for on-demand release, even a few times a day. It is not only much easier to detect and fix bugs in small batches, but also much wiser as the software becomes more bug-resistant. Finally, Continuous Deployment means that every change in the code should be deployed constantly and automatically in production. In an ideal scenario, this should be done without any human intervention.
- What is CI/CD – all you need to know
- CI/CD process—how to handle it in 2020
- How to set up and optimize a CI/CD pipeline
- Continuous monitoring and observability in CI/CD
- Business benefits of CI/CD
- CI/CD of CI/CD – how to avoid technical debt while delivering cutting edge software
- Sharing configuration between your CI, build and development environments