Twitter | Search | |
Adil Aijaz
How to increase your release frequency, in one image from . My take: If you do one thing, do CI. If you do two things, do CI and trunk based development. If you do 3 things, do CI, trunk based dev, and feature flags.
Reply Retweet Like More
John Tipper 17 Apr 18
Would be interested in how this diagram changes in a legally regulated industry, particularly finance.
Reply Retweet Like
Jez Humble 17 Apr 18
Here's the good news: it doesn't :D I've applied this framework in the US federal government, my continuous delivery co-author did it in finance (in London), and we both have a bunch of case studies and references if you have particular questions.
Reply Retweet Like
Manuel Recena Soto 16 Apr 18
Replying to @adilaijaz @jezhumble
When you have a component-architecture, where some components depend on other released components... the diagram needs to be revisited ;)
Reply Retweet Like
Jez Humble 16 Apr 18
Replying to @recena @adilaijaz
That's the point we were trying to make with the Architecture line. If you need to deploy everything together, you're not going to make it to daily deployments and you need to rearchitect. I have a talk on that here:
Reply Retweet Like
Paul Hammant 16 Apr 18
Replying to @adilaijaz @jezhumble
He he, your 2-thing scenario may segue into your 3-thing, which sometimes comes with connotations, too :)
Reply Retweet Like
Eric Minick 16 Apr 18
Replying to @adilaijaz @jezhumble
Also, know how fast you want to go. If you want to release once every week or two, you can get away with a whole lot less architectural change than if you want to ship many times a day.
Reply Retweet Like
Markus Karileet 16 Apr 18
Feature flags seems such an aweful idea. Why release if you're not using it?
Reply Retweet Like
Nils Breunese 16 Apr 18
In my experience trunk based development with feature flags saves a lot of time, because you don’t need to deal with large merge conflicts after branches have gone in different directions.
Reply Retweet Like
Alun Jones - Spoke at #RSAC, symptom-free 16 Apr 18
Replying to @adilaijaz @jezhumble
It would make my life a hell of a lot easier if there was a really good "Security" line on this chart.
Reply Retweet Like
Daniel Kraus 16 Apr 18
Replying to @adilaijaz @jezhumble
Would you say a branching model like GitHub flow (not Git Flow) falls under "Develop on branches […]" or "Pull requests to a release branch"?
Reply Retweet Like