<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc" -->

---
title: Let's not water down the terms Continuous Integration...
description: An opinion piece argues that the terms Continuous Integration (CI) and Continuous Delivery (CD) are being misused and diluted in industry conversation. Drawing...
canonical: https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Let's not water down the terms Continuous Integration and Continuous Delivery | daily.dev
og:description: An opinion piece argues that the terms Continuous Integration (CI) and Continuous Delivery (CD) are being misused and diluted in industry conversation. Drawing...
og:url: https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc
og:image: https://api.daily.dev/og/posts/3hzF6l6Vc.png
og:image:alt: Let's not water down the terms Continuous Integration and Continuous Delivery
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Let's not water down the terms Continuous Integration and Continuous Delivery

**[OctopusDeploy](https://daily.dev/sources/octopusdeploy)** · 6 min read · 5 upvotes · 1 comments

## Summary

An opinion piece argues that the terms Continuous Integration (CI) and Continuous Delivery (CD) are being misused and diluted in industry conversation. Drawing on Kent Beck's Extreme Programming Explained and Farley/Humble's Continuous Delivery book, the author clarifies that CI means merging to a shared mainline at least daily (not just automated builds), that CI is incompatible with long-lived feature branches, that CD means being deployable at all times (distinct from Continuous Deployment), and that CD requires CI as a prerequisite. The piece warns against letting these terms suffer semantic diffusion the way Agile and DevOps have.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://octopus.com/blog/watering-down-ci-cd>

## Questions this post answers

### What is the actual definition of Continuous Integration according to Kent Beck's Extreme Programming Explained?

Continuous Integration means merging all code changes into the main branch in version control frequently, with Kent Beck's 1999 book Extreme Programming Explained setting an upper limit of once per day. Modern practice expects merges far more often than that. Any branch or local changes older than a day, regardless of merge frequency from main into the branch, do not qualify as Continuous Integration because main remains unaware of those changes.

_Teams debating branching strategy can compare notes on CI definitions and practices via daily.dev._

### What is the difference between Continuous Delivery and Continuous Deployment?

Continuous Delivery means software is kept in a deployable state at all times and can be released at the press of a button, while Continuous Deployment removes that manual button-press and deploys every validated version automatically. Both require high automation and sufficient risk coverage to confidently answer 'can we deploy the software?' on a daily basis, as described by Dave Farley and Jez Humble in their 2010 book Continuous Delivery.

_Engineers deciding between manual and automatic release gates can track CD practices and debates on daily.dev._

### Can you practice Continuous Delivery without doing Continuous Integration?

No, Continuous Delivery requires Continuous Integration as a prerequisite. Dave Farley and Jez Humble explicitly include Continuous Integration as a required practice in their book Continuous Delivery, dedicating an entire chapter (page 55) to explaining why it is not optional for achieving reliable, low-risk software delivery.

_Developers untangling CI/CD requirements can follow deeper explainers on pipeline practices via daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@gautema** · 0 upvotes

> This has become my pet peeve for a few years. I hate how everyone refers to their build as CI and then destroying the term so most developers have no clue what CI is these days.

## Similar posts on daily.dev

- [Cloud-Based Continuous Integration & Continuous Delivery](https://daily.dev/posts/cloud-based-continuous-integration-continuous-delivery-i551e8dwb) · Spacelift · 1 upvotes · 0 comments

---

Tags: [#devops](https://daily.dev/tags/devops), [#cicd](https://daily.dev/tags/cicd)

[View this post on daily.dev](https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Let's not water down the terms Continuous Integration and Continuous Delivery","url":"https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc"},"datePublished":"2026-09-08T12:02:59.377Z","dateModified":"2026-09-14T06:44:57.871Z","description":"An opinion piece argues that the terms Continuous Integration (CI) and Continuous Delivery (CD) are being misused and diluted in industry conversation. Drawing...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/04630bca51e8cf9266661447aabe5d08?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/04630bca51e8cf9266661447aabe5d08?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"OctopusDeploy","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"OctopusDeploy","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/71110ae886d64eac9f3a01496feb2bd8","url":"https://daily.dev/sources/octopusdeploy"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"devops,cicd","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"OctopusDeploy","item":"https://daily.dev/sources/octopusdeploy"},{"@type":"ListItem","position":3,"name":"Let's not water down the terms Continuous Integration and Continuous Delivery"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc","comment":[{"@type":"Comment","text":"This has become my pet peeve for a few years. I hate how everyone refers to their build as CI and then destroying the term so most developers have no clue what CI is these days.","datePublished":"2026-09-09T12:27:09.951Z","url":"https://daily.dev/posts/3hzF6l6Vc#c-hb2CVdBPB","author":{"@type":"Person","name":"Gaute Magnussen","url":"https://daily.dev/gautema","image":"https://media.daily.dev/image/upload/s--cb7x1mno--/f_auto/v1728978621/avatars/avatar_FiBPwluDRGLmgCLiLeykw"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/let-s-not-water-down-the-terms-continuous-integration-and-continuous-delivery-3hzf6l6vc#faq","mainEntity":[{"@type":"Question","name":"What is the actual definition of Continuous Integration according to Kent Beck's Extreme Programming Explained?","acceptedAnswer":{"@type":"Answer","text":"Continuous Integration means merging all code changes into the main branch in version control frequently, with Kent Beck's 1999 book Extreme Programming Explained setting an upper limit of once per day. Modern practice expects merges far more often than that. Any branch or local changes older than a day, regardless of merge frequency from main into the branch, do not qualify as Continuous Integration because main remains unaware of those changes. Teams debating branching strategy can compare notes on CI definitions and practices via daily.dev."}},{"@type":"Question","name":"What is the difference between Continuous Delivery and Continuous Deployment?","acceptedAnswer":{"@type":"Answer","text":"Continuous Delivery means software is kept in a deployable state at all times and can be released at the press of a button, while Continuous Deployment removes that manual button-press and deploys every validated version automatically. Both require high automation and sufficient risk coverage to confidently answer 'can we deploy the software?' on a daily basis, as described by Dave Farley and Jez Humble in their 2010 book Continuous Delivery. Engineers deciding between manual and automatic release gates can track CD practices and debates on daily.dev."}},{"@type":"Question","name":"Can you practice Continuous Delivery without doing Continuous Integration?","acceptedAnswer":{"@type":"Answer","text":"No, Continuous Delivery requires Continuous Integration as a prerequisite. Dave Farley and Jez Humble explicitly include Continuous Integration as a required practice in their book Continuous Delivery, dedicating an entire chapter (page 55) to explaining why it is not optional for achieving reliable, low-risk software delivery. Developers untangling CI/CD requirements can follow deeper explainers on pipeline practices via daily.dev."}}]}
```

