{ "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": "\n

Yesterday I replied to a post on X<\/a>:<\/p>\n\n

\n

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>\n \n

\"CI is the practice of merging all developers' working copies to a shared mainline several times a day\"<\/p>\n<\/blockquote>\n\n

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>\n\n

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>\n\n

It isn't something that is configured or created - it's a process.<\/p>\n\n

Here's the thing<\/h2>\n\n

You can do CI without a CI pipeline and vice versa.<\/p>\n\n

You can have a CI pipeline but not do continuous delivery or deployment.<\/p>\n\n

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>\n\n

Whilst important, it's not \"CI\".<\/p>\n\n ", "format": "full_html", "processed": "\n

Yesterday I replied to a post on X<\/a>:<\/p>\n\n

\n

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>\n \n

\"CI is the practice of merging all developers' working copies to a shared mainline several times a day\"<\/p>\n<\/blockquote>\n\n

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>\n\n

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>\n\n

It isn't something that is configured or created - it's a process.<\/p>\n\n

Here's the thing<\/h2>\n\n

You can do CI without a CI pipeline and vice versa.<\/p>\n\n

You can have a CI pipeline but not do continuous delivery or deployment.<\/p>\n\n

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>\n\n

Whilst important, it's not \"CI\".<\/p>\n\n ", "summary": null } ] }