• Continuous Integration (CI) - the practice where developers continuously integrate/merge their changes back to the main branch as often as possible. The changes are then validated by creating a build via build-tools and running automated tests against the build to check that the application is not broken whenever new commits are integrated into the main branch

  Link to original

• Continuous Delivery (CD) - an extension of CI that begins with CI and ends with the release of verified artifacts (e.g. packages, jars/wars, virtual-machine images or container images) – these artifacts are published onto a central download server (e.g. binary repository managers)

  Link to original

• Continuous Deployment - goes one step further than CD, where changes/release-artifacts are automatically deployed to production, if they passed all stages of your production pipeline. If at any point a test failed the deployment to production is prevented. With Continuous Deployment there isn’t a Release Day anymore

  Link to original

How They Relate To Each Other

Subpages

• CI／CD Frameworks／Services
• Continuous Delivery (CD)
• Continuous Deployment
• Continuous Integration (CI)
• Deployment Strategy／Strategies
• SDLC Environments (Dev - Testing／QA - Acceptance／UAT - Staging - Demo - Production) - DTAP