2.2. Key Goals

CI/CD is a set of software engineering practices:

• Continuous Integration (CI): Automates the process of merging code changes and running tests.
• Continuous Deployment (CD): Automates the release of validated code to production.

CI/CD stands for Continuous Integration and Continuous Deployment. CI focuses on automatically merging code changes to a shared repository and running tests to ensure code quality. This means that every time developers make changes to the code, those changes are checked automatically through tests. CD, on the other hand, takes this a step further by automatically deploying the tested code to production, making it available for users without manual intervention. This streamlined process helps teams deliver software faster and with fewer errors.

Think of CI/CD like a bakery assembly line. In continuous integration, the bakers (developers) mix the ingredients (code changes) and constantly check for freshness (tests) before baking. In continuous deployment, once the cakes are baked and passed quality control, they are automatically placed in the storefront for customers to buy, without the need for a manager to approve each cake for sale.

• Reduce manual work
• Detect and fix bugs quickly
• Deliver features faster

The primary goals of implementing CI/CD are to reduce the amount of manual work involved in the coding and deployment process, making it more efficient. This automation allows teams to quickly identify and fix bugs because as soon as a developer submits code, it automatically goes through tests, helping catch errors early in the development cycle. Lastly, CI/CD enables faster delivery of features to end-users since the transition from development to production is streamlined and prompt.

Imagine a car manufacturing plant. If each part had to be manually installed without an automated process, it would take much longer to assemble and fix the car. However, with automation (CI/CD), the assembly line has machines that fit parts quickly, identify problems, and make the process seamless, allowing cars to roll out faster and with greater accuracy.

1. Developer commits code to repository (e.g., GitHub).
2. Code is built and tested automatically.
3. If tests pass, the application is packaged and deployed.
4. Monitoring and rollback mechanisms ensure stability.

The CI/CD lifecycle consists of four essential steps. First, when a developer commits their code to a version control system like GitHub, it triggers the CI/CD process. Second, the system automatically builds the code and runs tests to verify everything works as intended. If these tests are successful, the system moves to the third step, where it packages the application for deployment. Finally, the system continuously monitors the application in production and has rollback processes in place, so if any issues arise, it can revert to a previous stable version.

Consider the process of publishing a book. The author (developer) submits their manuscript (code) to a publisher (repository). The publisher then checks the manuscript for errors and assures it’s ready for print (building and testing). If everything looks good, they publish the book (deploy). If readers find faults in the book post-publication, the publisher can quickly release a new edition or make changes, ensuring customers have the best version available.

--