Discover and read the best of Twitter Threads about #ContinuousDelivery
Most recents (8)
Agile isn't dead, but it is widely misunderstood and more unusual than most people think.
a #Thread
1/12
a #Thread
1/12
I have spent the vast majority of my career working in what today we'd call 'agile' teams and organisations, but I hadn't heard the term until 20 odd years ago.
2/12
2/12
'Agile', with a capital 'A', has become the commonest form of SW dev, but it isn't 'agile' in the sense of the agile manifesto, it does not, as @pragdave says promote 'agility'
agilemanifesto.org
3/12
agilemanifesto.org
3/12
Posted: GitOps is a placebo stevesmith.tech/blog/gitops-is…
Why #GitOps:
1. is just a rebadging of #ContinuousDelivery and #InfraAsCode ideas
2. has no new ideas of substance
3. contains 'best practices' that won't always work
3. offers no benefits that can't be achieved without GitOps
Why #GitOps:
1. is just a rebadging of #ContinuousDelivery and #InfraAsCode ideas
2. has no new ideas of substance
3. contains 'best practices' that won't always work
3. offers no benefits that can't be achieved without GitOps
A few words on GitOps is a placebo stevesmith.tech/blog/gitops-is…...
I've disliked #GitOps from the start
. It went from "startup sharing ideas that worked for them" (good) into cargo culting (bad)
Git, Kubernetes, <insert tool here> are not special
I've disliked #GitOps from the start
. It went from "startup sharing ideas that worked for them" (good) into cargo culting (bad)
Git, Kubernetes, <insert tool here> are not special
#ContinuousDelivery and #InfraAsCode are tool agnostic, they're about principles and practices. They matter.
When someone says they've combined those principles and practices with some tools, to "extend" those principles and practices... I become cross.
When someone says they've combined those principles and practices with some tools, to "extend" those principles and practices... I become cross.
How should you decide if an incident merits a post-incident review?
The answer isn't "if it's a P1 or P2, forget P3s". In fact, it's the wrong question to be asking... #Operability 1/n
The answer isn't "if it's a P1 or P2, forget P3s". In fact, it's the wrong question to be asking... #Operability 1/n
Many orgs I work with have a policy of "do a review if the incident was a P1 or a P2". Lower priority incidents don't get a review.
This might be due to a high volume of P3s from untuned alerts, friction in the incident review process, lack of emphasis on improvement, etc. 2/n
This might be due to a high volume of P3s from untuned alerts, friction in the incident review process, lack of emphasis on improvement, etc. 2/n
At best, the incident review process involves team members working together to uncover a shared timeline and improvement actions.
I'd call this a "shallow analysis" that pre-dates an understanding of resilience engineering, operability, the work of @AdaptiveCLabs etc. 3/n
I'd call this a "shallow analysis" that pre-dates an understanding of resilience engineering, operability, the work of @AdaptiveCLabs etc. 3/n
Firstly, thanks to @clare_liguori for doing this. As someone with deep knowledge of deployment pipeline design and shallow knowledge of AWS, this is really interesting. I wish more companies did this 🙇♂️ 2/n
As someone who's been thinking about deployment pipeline designs for over a decade e.g. continuousdeliveryconsulting.com/blog/deploymen… and vimeo.com/370035221, it's always interesting to hear how orgs do deployment pipelines a) at scale and b) in unusual market conditions. AWS is a) and b) 3/n
#ContinuousIntegration Pro-tip (of course I mean single branch):
Start adopting the expand-contract pattern.
Start adopting the expand-contract pattern.
Expand-contract is what blue-green deployments do.
You expand by installing a new version of the app, and then you contract by removing the old version.
You expand by installing a new version of the app, and then you contract by removing the old version.
Expand-contract is also heavily used for zero-down time database schema changes.
Let’s say you need to rename a table column.
You expand by adding a new column with the new name.
Feed the new column with data.
Once the app uses the new column, contract by removing the old one.
Let’s say you need to rename a table column.
You expand by adding a new column with the new name.
Feed the new column with data.
Once the app uses the new column, contract by removing the old one.
First keynote of the morning at #AgileDevOpsCon is @aglover explaining The Netflix Approach to Continuous Delivery. 
The Netflix drive to #continuousdelivery was driven by developers, not operations.
@aglover #AgileDevOpsCon
@aglover #AgileDevOpsCon
They developed Spinnaker and then got other cloud providers to add to it to make it more pluggable. spinnaker.io
@aglover #AgileDevOpsCon
@aglover #AgileDevOpsCon
Thread!
If you've decoupled deployments from customer launches, well done 👍
*But* bear in mind #ContinuousDelivery is about increasing throughout to meet customer demand. So it's the frequency of customer launches you need to increase, not just deployments 1/n
If you've decoupled deployments from customer launches, well done 👍
*But* bear in mind #ContinuousDelivery is about increasing throughout to meet customer demand. So it's the frequency of customer launches you need to increase, not just deployments 1/n
Deploying more frequently to production reduces technology risk, overheads, inefficiencies, etc. It's a good thing.
However, it's customer launches that create opportunities for validated learning 2/n
However, it's customer launches that create opportunities for validated learning 2/n
#ContinuousDelivery was named after the first principle of the Agile Manifesto agilemanifesto.org/principles.html
"Our highest priority is to satisfy the customer through early and continuous delivery of valuable software"
It is a means to achieve customer satisfaction 3/n
"Our highest priority is to satisfy the customer through early and continuous delivery of valuable software"
It is a means to achieve customer satisfaction 3/n
Hi @InfoQ, your #GitFlow article is flat out wrong. It is 100% incompatible with #ContinuousIntegration and #ContinuousDelivery. continuousdeliveryconsulting.com/blog/organisat… / @danielbryantuk
Here's an @InfoQ article I did in 2015, explaining why #GitFlow is incompatible with CI let alone CD infoq.com/news/2015/10/b…
Here's an @InfoQ video of a talk I did in 2015, which includes an explanation of why #GitFlow is incompatible with CI infoq.com/presentations/…
