Published on 15 December 2014 by

The following content is a shortened excerpt from the white paper, The Tools For Continuous Delivery. Download the paper to learn more about the benefits of continuous delivery, and how to launch it in your organization.

When it’s well executed, continuous delivery allows an organization to respond more quickly to its market and to customers, both internal and external. It also makes life saner for people in IT operations, software development and quality testing teams. Instead of long periods of development punctuated by looming deadlines, big dramatic releases and panicked remediation of serious bugs, software releases are small, predictable and less dramatic… even boring :-)

Top Benefits of Continuous Delivery

Deliver software with fewer bugs and lower risk.

When you release smaller changes more frequently, you catch errors much earlier in the development process. When you implement automated testing at every stage of development, you don’t pass failed code to the next stage. And it’s easier to roll back smaller changes when you need to..

Release new features to market more frequently — and learn.

Releasing new features early and often — even in a minimally viable state — means you get more frequent feedback, giving you the ability to iterate and learn from your customers. Enlisting customers as development partners gives them a sense of co-ownership and loyalty, and makes them more likely to forgive when you stumble.

Respond to marketing conditions more quickly.

Market conditions change constantly. Whether you’ve just discovered a new product is losing money, or that more customers are visiting your site from smartphones than laptops, it’s much easier to make a fast change if you are already practicing continuous delivery.

Life is saner for everyone: IT operations, software development, QA, product owners and business line owners.

Continuous delivery means the responsibility for software delivery is distributed much more widely, and this shared responsibility and collaboration make life better. Continuous delivery also take a lot of stress out of software release. Releasing smaller changes more often gets everyone used to a regular, predictable pace, leaving room tocome up with ideas and actually enjoy your the work. Best of all, a successful release becomes a shared success, one you can all celebrate together.

Download the white paper to find even more comprehensive information on the benefits of continuous delivery, plus sections on how to launch continuous delivery in your organization — and the right tools to use!

Aliza Earnshaw is managing editor at Puppet Labs.

Learn more

Share via:

I'm surprised Collaborator (from SmartBear) wasn't included in the white paper. It's one of the more useful Code Review tools I've used.

Thanks so much for offering another code review tool to consider, Michael! What things do you like best about Collaborator? It's also good to know about AppVeyor for Windows.

It tracks comments and defects separately, with both tracked across code changes. It supports having required and optional sign-off to complete the review, with ways to track whether that's happened (that get updated when new defects or code are added to the review). It also has pretty readable code diffs. Unfortunately it's gotten clunky over time, but I think it supports a better workflow than Github - and possibly Stash and Gerrit, from what I can see of their interfaces.

here is my requirement, does it suitable.
1. Installations of our product.
2. Installations of thrid party softwares(java, oracle and etc...)
3. automating above installations.
4. we have 20 VM(virtual servers), can i handle them with one single URL.
5. running multiple installation at a same time.
6. viewing the results after running the script.
7. do have ur own language to write a script or global language u use.
does this tool met my above requirement?

Hi, Kumar,

We aren't able to supply tech support here in our blog comments, but you can always go to or the Puppet users discussion group on Google (!forum/puppet-users) and find people discussing continuous delivery workflow with Puppet. You can also read the white paper linked in the above blog post.

The content of this field is kept private and will not be shown publicly.

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.