Archives for the tag: continuous delivery

This is the forth in our five-part series from guest blogger J. Paul Reed—build engineer, automation enthusiast, and host of The Ship Show podcast. Any discussion on the transition toward continuous delivery of your software would be incomplete if it neglected the cultural aspects of such a deep change. In many conversations about the larger concept of DevOps (which CD is often a part of), much time is spent bandying about the question of tools versus culture: how each are relevant, where

Continue reading »

This is the third in our five-part series from guest blogger J. Paul Reed—build engineer, automation enthusiast, and host of The Ship Show podcast. In the last two articles, we covered the business value proposition for implementing continuous delivery, as well as some areas you'll need to keep your eye on in your own organization to nurture a transformation towards continuous delivery (CD). Many times, those shepherding a company's continuous delivery transformation find it a daunting

Continue reading »

This is the second in our five-part series from guest blogger J. Paul Reed—build engineer, automation enthusiast, and host of The Ship Show podcast. Jez Humble, author of Continuous Delivery and one of its founding fathers, has an informal survey he likes to give to audiences. It starts with a simple question: "Raise your hand if you do continuous integration." A sea of hands always rise. Then he says "Put them down if all of the developers on your team don't check into the main code-line

Continue reading »

This is the first post in our five-part series from guest blogger J. Paul Reed – build engineer, automation enthusiast, and host of The Ship Show podcast. Software development is moving towards continuity. The recent emphasis on continuous integration, built-in testing, constant monitoring, and feedback telemetry all point toward an overall trend in the software industry: increasing the ability to react. To become real-time businesses. As organizations explore what these changes mean for them,

Continue reading »

In February, I had the pleasure of speaking with the London Atlassian User Group (AUG) about some of our experiences with continuous delivery and deployment at Atlassian. The slides for this are available online, but the talk generated a lot of discussion at the time and I'd like to recap some of it here. To give a bit of context, I work in the business platform team; we're responsible for developing the tools that allow the business to interact with the customer. In particular, we develop the

Continue reading »

We all have the tendency to avoid things that are going to be difficult – whether physical, logistical, or otherwise. And we do this knowing full well that if we just faced the tough things head-on, it would result in a much lower degree of total difficulty in the long run. (For example, I once went three years without seeing a dentist, and was so afraid of what might be revealed that I continued to avoid it for another four years.) Ahhh, humans. Gotta love us. In the software world, the "dentist"

Continue reading »