9 ms·
Fully automatic deploys are distinct from fully automated ones. I insist on the latter but not everyone is comfortable with the former. Large / legacy / lumberi
by koolba 9y ago
Fully automatic deploys are distinct from fully automated ones. I insist on the latter but not everyone is comfortable with the former. Large / legacy / lumbering institutions (think big banks) in particular want a change ticket, window or some other control before a release makes it's way to production.
The middle ground I've found is to have fully automatic deploys in lower environments and automate the entire process for production. But rather than have releases flow there automatically, production is handled by pressing a single "Deploy whatever is in UAT to prod" button (i.e. the "Big Red Easy Button"). You then give access to that button to somebody else in the org (ex: a UAT team, a release team, your manager) and everybody's happy. It also conveniently gives you an excuse to never fill out production release paperwork as "It's not my job, I'm not allowed to release to production!"
- wpietri 9y agoYou raise an important point. I think there's a big distinction to be drawn between people's feelings and actual business needs. People everywhere like feelings of control. And the more layers of management a company has, the more executive feelings come to predominate over on-the-ground business facts. But in practice, bureaucratic change-control processes don't actually produce better code or safer systems. In my experience, they make things worse, because large batches and slow feedback loops make bugs easy to add and hard to find. One good next step after the middle ground you describe is continuous deployment of code, but using feature flags and A/B testing tools to control visibility and impact of features. As you say, if you give people some big, obvious controls, they feel in control. Decoupling code release with business impact lets me get on with what I care about. And it lets them learn to be bolder, more engaged in the process of delivering value to users.
- hinkley 9y agoThere’s a new group learning CD that mistakenly believes that automatic deploys are CD. Most of these came to the concept after it had supplanted discussion about CI. Automating a deploy is relatively straightforward but doesn’t provide much value if that’s all you do. Local reproduction of build steps, metrics, historical data, building out test infrastructure, all of this is important for scaling up a team and keeping regressions low.
- devonkim 9y agoI think there really needs to be a separate acronym from CD to better distinguish deployment from delivery (similar to authn v. authz in security nomenclature). Nobody with the right mindshare seems to have made this a priority though because automated deployments are probably not cost-effective in many organizations but delivering a change, however, is something that has solid value everywhere. Coming up with a change ticket with the impact of a change and what’s typically paperwork in many places absolutely has value and will help people move faster with lower risk while making management feel like they have control (because most continuous code based controls of delivery mechanics tend to be more democratic in practices, not manager-oriented). Maybe it could be CDD (continuous delivery description) vs CDE (continuous delivery deployment)?
- hinkley 9y agoI hold that on a well functioning team the mid level developers are delivering most the the code. The senior people are dealing with clearing roadblocks and cross cutting concerns like stability, security or performance. This is not a blame the victim structure. It’s more like a pedestrian version of NASA’s incident system. To do this the process needs to be self service. You can find mid level people pretty easily. Anyone who wants a promotion or become an SME should have tools to do a lot of that work themselves instead of having to extract it from the leads or follow the School of Hard Knocks. Good automation supports this, bad automation makes this harder.