Over a million developers have joined DZone.

Jenkins World Round Up: Focus on Release Orchestration

DZone's Guide to

Jenkins World Round Up: Focus on Release Orchestration

The variety of industries came as no surprise to us, given that releasing the best, most reliable software while maximizing revenues is an imperative for any business.

· DevOps Zone ·
Free Resource

Discover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.

So Jenkins World is a wrap, and what a great show it was. The event kicked off last Wednesday, with lots of folks stopping by our booth to get a firsthand demo of XL Release, our release pipeline orchestration software. XL Release lets enterprises manage and control the most advanced release pipelines with ease.

XL Release release pipeline orchestration software demonstrated at Jenkins World

People from companies running the gamut from airlines to telecomm to pharmaceuticals were eager to learn how pipeline orchestration could help them. The variety of industries came as no surprise to us, given that releasing the best, most reliable software while maximizing revenues is an imperative for any business.

The key is having full visibility into and control over your software release pipeline so you can deliver high-quality applications without missing a beat. Intelligence is critical as well, since you can’t understand where you need to improve if you don’t track the appropriate metrics.

Jenkins: Great for CI, Not for Release Orchestration

We spoke with several people at Jenkins World who thought the path of least resistance was to repurpose their existing tools—Jenkins was top of mind for obvious reasons. There’s no doubt that Jenkins is a brilliant tool. It excels at automating technical steps involved in building and testing applications. But from its beginnings, it was built for continuous integration, not pipeline orchestration.

For example, you can use Jenkins to enforce workflow but not model the delivery process. The result is extensive scripting and manual script updates every time something changes. Think about the typical enterprise with its array of deployment environments, multitudes of simultaneous releases, geographically distributed operations and teams, variety of stakeholders, and byzantine compliance requirements. Now ask yourself if scripting will scale. The answer is easy. It won’t.

XL Release: Purpose-Built for the Enterprise

At Jenkins World, we had the chance to show people that there really is a better way: XL Release. We demonstrated how they could orchestrate the entire release process from end to end with full automation, visibility, control, and intelligence in a way that allows both technical and business teams to participate. And we walked them through how they can use XL Release to build on Jenkins continuous integration, as well as myriad other tools like Chef, Puppet, JIRA, ServiceNow, and XL Deploy.

In short, XL Release is purpose-built for the enterprise, and that got a lot of people excited. If you haven’t had a chance yet to see XL Release for yourself, here are some options:

Other Resources

Live Webinar: Jenkins CI + XebiaLabs for Release Orchestration: A Recipe for Continuous Delivery Success. Join us on September 29 as we discuss (among other things) how to complement your current investment in Jenkins CI with XebiaLabs to accomplish true enterprise Continuous Delivery.

White paper: “Release Pipeline Orchestration: An Essential Practice for Continuous Delivery at Enterprise-Scale. Learn the importance of enterprise-grade pipeline release orchestration solutions and where Jenkins and other tools fit in the big picture.

Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.

devops ,orchestration ,jenkins world ,software

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}