Updated: October 16, 2024 (January 17, 2022)

  Sidebar

What Is Continuous Integration, Delivery, and Deployment?

My Atlas / Sidebar

353 wordsTime to read: 2 min
Rob Sanfilippo by
Rob Sanfilippo

Before joining Directions on Microsoft, Rob worked at Microsoft for 14 years where he designed technologies for Microsoft products and... more

Continuous integration, delivery, and deployment (CI/CD) have become popular strategies as Agile development methodologies and DevOps practices have proliferated. CI/CD brings fast-moving application life cycles that update functionality and can ensure production availability better than older practices in which cycles moved more slowly and often brought substantial changes in large batches.

CI/CD terminology is often used loosely, but the terms refer to the following:

Continuous integration (CI) is a strategy in which every code check-in to a primary source control system branch triggers a full build and possibly automated tests to ensure that the check-in does not break the build or application release criteria, such as functionality and security. CI reduces build break debugging difficulties that occur when builds are not performed until many check-ins have been made.

Continuous delivery (CD) is a strategy in which development teams produce new application versions that can be used in production in short (for example, 30-day) cycles. The frequent releases provide customers with regular feature updates and bug fixes.

Atlas Members have full access

Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.

Membership Options

Already have an account? Login Now