Welcome!

XebiaLabs | Continuous Delivery and Agile DevOps Tools

XebiaLabs Blog

Subscribe to XebiaLabs Blog: eMailAlertsEmail Alerts
Get XebiaLabs Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Blog Feed Post

3 Approaches to Release Orchestration Using Jenkins

Today’s software world is divided into phases. With each phase comes a list of tasks waiting to be completed. And for every task there is a tool with a specific purpose in the pipeline. Wouldn’t it make sense for all of these tools to work in sync with each other?

 

Jenkins is a fantastic resource to increase your pipeline’s capabilities for Continuous Integration. However, at its core, Jenkins is a scripting tool, and like all scripting tools, presents scaling challenges that come with meeting increased business needs. This is where release orchestration software helps. XL Release allows you to model your software release process and save it as a template so you can execute your entire pipeline with a simple push of a button.

With plug-ins on both the Jenkins and XL Release side, users can effortlessly integrate the two, ensuring a peaceful and harmonious process. To help you plan your unique DevOps pipeline, here are three examples of how to bring Jenkins and XL Release together. Pick the one that best suits your enterprise.

 

Approach 1: XL Release First

screen-shot-2016-10-12-at-10-39-44-amhttps://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 768w, https://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 1024w, https://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 1289w" sizes="(max-width: 305px) 100vw, 305px" />

The XL Release First approach works great in scenarios where releases are triggered by regular process activities that have no precise order. You can start in one of three places: from XL Release itself, automatically from an outside tool using one of XebiaLabs’ many plug-ins, or anywhere else via XebiaLabs’ APIs.

The first phase of the pipeline involves building release artifacts or verifying the build. Using XL Release’s specialized plug-in architecture, you can configure access controls, configure returning artifacts and parameters, and track durations for reporting. As Jenkins continues to appear in subsequent phases to retrieve artifacts and fingerprints or even verify unit tests, you can use this information to make informed decisions on whether to move on to future phases.

Although Jenkins is great for integrating a variety of tools that it can trigger, it’s important to remember that the orchestration from one pipeline phase to the next happens in XL Release. With this XL Release first approach, you can reap benefits from both tools in one effortless, unified orchestration.

Approach 2: Jenkins First

screen-shot-2016-10-12-at-10-40-45-amhttps://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 768w, https://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 1024w" sizes="(max-width: 383px) 100vw, 383px" />

The Jenkins First approach is meant for releases triggered by code events or events on a regular schedule. Starting with Jenkins gives you access to the ample options and integrations it provides to listen for events. This approach calls for the use of the Jenkins XL Release plug-in to trigger a new release or pipeline run in XL Release. This lets users continuously call back to Jenkins as often and from whatever phases they’d like while still orchestrating the pipeline from within XL Release.

 

Approach 3: Hybrid Pipeline

screen-shot-2016-10-12-at-10-40-57-amhttps://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 768w, https://blog.xebialabs.com/wp-content/uploads/2016/10/Screen-Shot-2016-1... 1024w" sizes="(max-width: 362px) 100vw, 362px" />

Finally, the Hybrid Pipeline approach is typically used when on-boarding existing applications. As long as the plug-ins are present in both XLR and Jenkins, this approach provides extra flexibility to trigger your release pipeline whenever and however many times needed. This approach allows for multiple pipelines to come together. As these tools make their way down the pipeline, a series of triggers can be set off to communicate jobs in the other tools. By automating Jenkins and XL Release to work in tandem, you allow yourself to enjoy the best of both tools.

 

Like French fries and milkshakes or breakfast for dinner, the combination of Jenkins and XL Release is another example of two things that go together in the most perfect way possible. Soon you’ll begin to wonder how you ever got along without it.


Want to learn more about Release Pipeline Orchestration and the part it plays in successful Continuous Delivery, check out: Jenkins CI + XebiaLabs for Release Orchestration: A Recipe for Continuous Delivery Success.

The post 3 Approaches to Release Orchestration Using Jenkins appeared first on XebiaLabs.

Read the original blog entry...

More Stories By XebiaLabs Blog

XebiaLabs is the technology leader for automation software for DevOps and Continuous Delivery. It focuses on helping companies accelerate the delivery of new software in the most efficient manner. Its products are simple to use, quick to implement, and provide robust enterprise technology.