92 lines
3.5 KiB
YAML
92 lines
3.5 KiB
YAML
uuid:
|
|
- value: 0a04ac23-4d64-40e8-8e94-ead3cab7129d
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'CI !== CI Pipeline'
|
|
created:
|
|
- value: '2024-07-02T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:10+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/07/02/ci-not-ci-pipeline
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Yesterday I replied to <a href="https://x.com/ianmiell/status/1304103008242991111">a post on X</a>:</p>
|
|
|
|
<blockquote>
|
|
<p>I have worked on many teams that use CI tooling and call their process CI, but I have never seen CI actually done as defined on Wikipedia:</p>
|
|
|
|
<p>"CI is the practice of merging all developers' working copies to a shared mainline several times a day"</p>
|
|
</blockquote>
|
|
|
|
<p><a href="/blog/continuous-integration-vs-continuous-integration">I've written about this before</a> and I think the term CI or CI/CD is one of the most misused or misleading in software development.</p>
|
|
|
|
<p>CI, or continuous integration, is, as the post days, the process of everyone merging their changes at least once, or usually several, times a day.</p>
|
|
|
|
<p>It isn't something that is configured or created - it's a process.</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>You can do CI without a CI pipeline and vice versa.</p>
|
|
|
|
<p>You can have a CI pipeline but not do continuous delivery or deployment.</p>
|
|
|
|
<p>What most people think of as CI or CI/CD is a set of automated checks that run when code is updated - usually on a feature or topic branch.</p>
|
|
|
|
<p>Whilst important, it's not "CI".</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Yesterday I replied to <a href="https://x.com/ianmiell/status/1304103008242991111">a post on X</a>:</p>
|
|
|
|
<blockquote>
|
|
<p>I have worked on many teams that use CI tooling and call their process CI, but I have never seen CI actually done as defined on Wikipedia:</p>
|
|
|
|
<p>"CI is the practice of merging all developers' working copies to a shared mainline several times a day"</p>
|
|
</blockquote>
|
|
|
|
<p><a href="http://default/blog/continuous-integration-vs-continuous-integration">I've written about this before</a> and I think the term CI or CI/CD is one of the most misused or misleading in software development.</p>
|
|
|
|
<p>CI, or continuous integration, is, as the post days, the process of everyone merging their changes at least once, or usually several, times a day.</p>
|
|
|
|
<p>It isn't something that is configured or created - it's a process.</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>You can do CI without a CI pipeline and vice versa.</p>
|
|
|
|
<p>You can have a CI pipeline but not do continuous delivery or deployment.</p>
|
|
|
|
<p>What most people think of as CI or CI/CD is a set of automated checks that run when code is updated - usually on a feature or topic branch.</p>
|
|
|
|
<p>Whilst important, it's not "CI".</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|