The latest expert opinions, articles, and guides for the Java professional.

Release Management for Enterprises

Concluding Remarks, Additional Resources and a Goodbye Comic ;-)

Just a few closing remarks about everything we said–you can take this as your Too Long; Didn’t Read (TL;DR)


Whew. If this all seems like a lot to handle….then get over it! You’re an intelligent engineer! ;-)

If you weren’t aware of the latent benefits of embracing the fomenting DevOps movement, then we set the stage a bit for you in the report. Then we went on to propose a toolset for you to use for building your own automated release pipeline, which include solutions from GitHub, Artifactory, Bamboo, Arquillian, Selenium, JBoss AS 7 and LiveRebel…use of tools like Eclipse, Maven, JUnit and others is expected.

We showed you have to bake your very own automated release pipeline in 6 essential steps to build your very own streamlined, automated release pipeline. Over time, you may customize the pipeline based on your needs, but the utility and benefit usually remains the same. You get:

  • Accountability: Progressing to the next stage indicates sign-off on the successful completion of the previous one.

  • Traceability: Build numbers indicate changelogs and versions deployed on specific environments.

  • Release Management: Automated with a few clicks.

  • Communication: Build, test and deployment results communicates release progress and audits for later reference.

  • Repeatability: Tasks are automated and consistently repeated.

  • Adaptability: While the template helps automate, it can be modified as needed.

Adopting DevOps is a prerequisite to streamlining and automating your release processes. Without active, team-wide collaboration, grasping the big picture and unifying the release process is hard to achieve. Once successful, it can help take software to users quickly and frequently without compromising on quality.

Everybody wins. Users get well-tested features as soon as they’re available, developers build software that works as opposed to shelfware, QA teams focus on test coverage rather than running manual tests, operations teams focus on improving infrastructure and processes rather than running manual application updates. Your job gets easier, and your customers get better products from you. Happy Festivus!

To say it another way: your business wins with reduced time to market, happy customers and happy employees, which results in increased revenue.

C'mon, get the PDF already! ;-)

Responses (2)

  1. Avatar  


    August 22, 2013 @ 1:58 pm

    Was there a reason behind using GitHub, instead of Atlassian’s Stash product?

  2. Avatar  

    Oliver White

    August 26, 2013 @ 7:02 am

    Not in particular, we just wanted to experiment with other tools out there and expose our readers to as many different technology companies as possible. We also produced a similar report last year with free or OSS tools entitled “Pragmatic Continuous Delivery with Jenkins, Nexus and LiveRebel” — check it out:

RSS feed for comments on this post.

Leave a comment