Continuous Integration (CI):

Involves integrating changes to the project repository and testing them.

Aims to prevent “breaking the build”, i.e., causing system tests to fail.

Promotes a “quality culture” among team members who aim to avoid disrupting the build.

Requires a fast integration process so developers don’t have to wait for test results.

Every time a change is pushed to the system’s shared code repository, an integrated version of the
system is created and tested.

The advantage of continuous integration is that it is faster to find and fix bugs in the system.

Continuous Delivery:

Ensures the system is ready for delivery to customers after changes.

Involves testing in a production environment to check for system failures or performance issues.

Does not necessarily mean immediate release to users for deployment.

After making changes to a system, you ensure that the changed system is ready for delivery to
customers.

The CI tool is triggered when a file is pushed to the repo. It builds the system and runs tests on your
development computer or project integration server.

Continuous Deployment:

Practical only for cloud-based systems.

If the product is sold through an app store or downloaded from a website, continuous integration and
delivery are beneficial.

Continuous deployment means that the software will be released immediately to users for deploymSent.