CI/CD

The main difference is that testing and code building is performed in automatic mode.

Principles of work

CI (Continuous Integration) – continuous integration. While writing code, developers constantly make changes that are uploaded to the repository. For automatic testing and verification they use specialized services, for example, Github, which create scripts. A log is kept for each step, which records any changes.

CD (Continuous Delivery) – Continuous Delivery. Responsible for automatic deployment of the build in any environment: production, testing or development environment. For example, after editing the code, it is automatically placed in the testing area.

The methodology is used in companies that frequently modify code during development, but still produce stable releases. Developers get an automated process for testing and deploying the application, which allows them to focus on continuous software improvement.

Stages of the methodology

The CI/CD cycle is conventionally categorized into 7 stages:

1. Creation. Programmers write a certain part of the code and then test it manually. If the test is successful, the parts are merged into a single code and transferred to the working development branch.

.

2. Assembly. The second stage uses special software for product version control, for example, Git. The program runs an automatic build with the changes made, and then tests the resulting code. Criteria for successful passing are set up in manual mode.
3. Manual test. After passing the autotest in the software, the product is sent to a team of testers for testing. They manually check the written code and look for bugs.
4. Release. After the successful completion of the third stage, the code enters release. A working build is created to update the current software product to the current version.
5. Deployment. The received update is broadcast on the official developer servers to update the software to the latest version.
6. Support and monitoring. Programmers monitor customer feedback and prepare a list of future changes.
7. Planning. The last step creates an approved change list for the next versions. At the end of this step, the development cycle ends and starts again.

With this principle of work, users get a fully working release. If they find a bug or error, they report it to tech support.