Category: CI/CD
-
Some Counter-intuitive Truths about CI/CD
Intuition: “Integrating more frequently causes more merge conflicts.” Reality: It causes more occasions for potential merge conflicts, each one less likely to occur, easier to resolve, and cheaper to discard if necessary. Intuition: “Frequently merging downstream (pulling main into feature branch) solves the problem of merge conflicts.” Reality: It only…
-
The CI/CD Misconception
The terms CI (continuous integration), CD (continuous delivery), and the umbrella term CI/CD are often misunderstood and misused. Many think that continuous integration is primarily about automation and tooling, i.e., having an automated build pipeline, often evidenced by them referring to their pipeline as “the CI”. They are unaware that…
-
CI/CD is Not a Tool
CI/CD is something you do, not something you have. Having an automated build and deployment pipeline is part of it, but there’s nothing inherently “continuous” about Jenkins or GitHub Actions. I have no problem with tool-focused terms like “CI pipeline” if the intention is to imply that the tool is…
Raimund Krämer 