DEV Community

Discussion on: Let's stop fooling ourselves. What we call CI/CD is actually only CI.

Collapse
 
jessekphillips profile image
Jesse Phillips

I think the terminology in unfortunately overloaded.

gitlab.com/jessephillips/blog/-/bl...

Industry has shoved everything into CI and then reserved CD for production. Realistically there is CI, something in the middle, then CD.

Organizations have done CI for a long time, but then they want to do "something in the middle". It is a hard sales push, "let's implement CI!"... "umm, didn't we do that last year?" "yes, but we just do this every year"

I think it is because to realize there is ambiguity in where the lines exist and ask for clarification.

Collapse
 
antweiss profile image
Ant(on) Weiss

yes, ambiguity definitely leads to misinterpretation. but my point is that CD in cloud native world is a totally different concern - not just an extension of our pipeline. CI or "something in the middle" can all be implemented by a basic workflow automation tool. CD requires smarter, domain-specific algorithms and strategies.