Struggling to get software released on a daily basis? Wondering how to apply the same techniques that make companies successful with continuous deployment? What if your company isn’t in a greenfield situation and carries build legacy? What if developers on your team have a mindset that is the opposite of continuous deployment? This is a story about the Confluence development team and their journey from struggling to release once a week to releasing every day. Learn about the challenges the team faced and the interesting solutions they came up with to reach their goals while avoiding many rabbit holes along the way. In this session, you will get many interesting insights and techniques that you can apply immediately in your own organization's journey towards continuous deployment.
Products covered:
Confluence, HipChat, Bamboo
22. ResultsBeliefsExperience Actions
The Oz Principle
The way you’ve been
shaped
Beliefs are based on
your experience
You take actions
based on your beliefs
The outcome of our
actions
42. Early result
Move the needle
Measure everything
Visibility
Create awareness in the wider
team
Gather data to allow data driven
decisions and prioritisation
Focus on quick wins to move the
needle
43. • Big cool statistic
• 2,56
9
• Add-Ons in Marketplace
Sustainable System
https://flic.kr/p/awVLLs
49. The impact
of flakes
Broken windows
Culture
Build times
Due to restarts build times get out
of control really quickly
Builds will go red people will start to
ignore this; Culture of green out of
the window
It starts with one, many will follow
soon
50. Retries as a pain killer
Automatic retries to relieve some
pain. Remember this is a
workaround
Early result
51. • Big cool statistic
• 2,56
9
• Add-Ons in Marketplace
Fix the root cause
https://flic.kr/p/J44Nm