Blog

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

Release Management for Enterprises

6. Orchestrate Everything

We now have an automated release pipeline and are ready to practice Continuous Delivery. We set up a Github repo, Continuous Integration builds, automated tests, and zero downtime, automated deployments to take apps right to our end users. Magical. :)

Stages are executed sequentially and jobs within a stage are run in parallel for efficiency.

You may prefer to trigger the Deploy job manually. This way you get the predictability and repeatability of a Continuous Delivery pipeline, but still control the last step.

You can always add more stages to this pipeline later. For example, to deploy to QA or staging environments first. So you could end up with a plan that looks like this.

Remember, “nullam transitionem fieri per saltum” (no transition occurs by a leap), start small and move in the right direction.



DOWNLOAD THE PDF

Responses (2)

  1. Avatar  

    jennifer

    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: http://zeroturnaround.com/rebellabs/zt-labs-tutorial-pragmatic-continuous-delivery-with-jenkins-nexus-and-liverebel/

RSS feed for comments on this post.

Leave a comment