Hi folks, the poll didn’t get a ton of votes, but the few it did get were consistent with the anecdotal findings I’ve been seeing: dedicated CI/CD team seems to be getting increasingly uncommon, instead being owned by either SRE / Platform Eng or some part of the core eng team. There are a few other emerging trends that are interesting: - more & more security tools integrated into the CI pipeline, and require more babysitting or even manual operation per build (security is of course very important.. but so is delivery velocity) - in the case where its handled out of core eng, CI can get fragmented across teams, requiring “CI for CI” or a manual approach to stitch everything together - deployment no longer goes to prod for various reasons, but to staging (which is not exactly like prod), and there are a set of poorly documented things that must be done to take a build from staging to prod, manually the term “CI/CD” itself seems to be falling out of favor, with some folks preferring to call it things like “build automation,” possibly because it’s not longer fully Continuous I’d love to hear any thoughts, opinions, personal experiences folks here would like to share! (PS if anyone feels there is a better channel for this, pls advise)

Or another way of saying that is “The problem has changed” in 2023

Those teams were a reaction to how much yak hair you needed to shave to do them effectively 5 years ago. That is simply not the case anymore.

If you’re a Web2.0 CRUD app sure, CI/CD is pretty static and boring now. But if you’re looking at the next wave of applications that are being built its quite different. (we’re not even talking about the serverless type architectures and how to weave them together)

(there’s also the SSC type work that has to be done that was abysmal 5 years ago)

work is still going on there today, NIST is collecting comments on the latest draft through next month

That article is great BTW! I will need to read it more detail later on, but even at a surface glance it touches on some key points. CD is great for consumer apps, where no one user has any say in what happens. but for enterprise, it was never a good fit. Enterprise customers are not generally interested in having the software they use change at random intervals. It also doesn’t fit well at the “edge” for non-cloud compute platforms, which have a totally different set of constraints.

(talking about CD all the way to prod here, as opposed to an internal staging env)

we solve the enterprise and the edge problem

so we saw this use case entirely

it’s exactly what you described as the problem statement