Blog

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

Pragmatic Continuous Delivery with Jenkins, Nexus and LiveRebel

Conclusions

The most important thing to learn is that it is now fairly easy to build a Continuous Delivery pipeline and most of the complicated workflows in your organization can be modeled using Jenkins, Nexus and LiveRebel.

The pipeline that we built has the following key aspects:

Jenkins is used to orchestrate the over- all workflow and create a pipeline that takes patches from VCS and produces release candidate builds that have passed all the hurdles. Scripting Jen- kins is essential for more complicated scenarios.

Nexus is used to create synchroniza- tion points for long-running or manual processes as well as long-term storage of records and artifacts.

LiveRebel is used to manage servers, applications, versions and deployments in a centralized and scriptable way. It is responsible for applying changes to en- vironments without a negative impact on users or systems.

Email can be used to incorporate manual workflows into the CD pipeline.Alternatively REST or similar APIs can be used to integrate internal tooling into the pipeline in an asynchronous way.

Text metadata is a simple, but ef- ficient way to record the log of eve- rything that is important in the life of a build. It should thread through the pipeline and be available everywhere an artifact is deployed, including in production.

With those tools at your disposal, and the Continuous Delivery philosophy tucked into your belt, it isn’t hard to build an automated, trackable, testable and recoverable pipeline for production updates that bring continuous advantage your users, your staff or your organization.

Please leave comments below, or tweet us at @ZeroTurnaround.


DOWNLOAD THE PDF

No Responses

No comments yet.

RSS feed for comments on this post.

Leave a comment