Extending Jenkins for Continuous Delivery
We all know Jenkins is a brilliant tool for Continuous Integration. It excels at automating the technical steps involved in developing, building, and testing applications. As your Continuous Integration (CI) process matures and you look to expand to Continuous Delivery (CD), you need to look at orchestrating the entire release process from end-to-end.
XebiaLabs Release Orchestration builds on the CI-focused automation of Jenkins to add the equally important process integration side. Delivering an application from Development environments to customer-facing environments is complex. Continuous Delivery needs to encompass your company’s Change, Release, and Project Management policies and processes… and this is where management-oriented dashboards, team analytics, and reporting APIs are critical.
“If you’re looking to improve, accelerate, and streamline your end-to-end software delivery, and enforce compliance requirements in a repeatable, auditable process, you want XebiaLabs.”
– Vito Iannuzzelli, Assistant VP of IT, NJM Insurance Group
Define Your End-to-end Process in 30 Minutes, Not 30 Hours… and Version this Process to Ensure Repeatability
- Visualize and share release status in clean, clear, configurable dashboards
- Tweak running releases––while maintaining enterprise-class security and auditing––to understand where “reality gets in the way of the plan”
- Continue to transform your organization with data-driven improvement: use metrics and analytics to see bottlenecks and speed up your pipelines
- Easily create custom extensions without learning complex integrations
Continuous Delivery is Not Just “A Few More Jobs in my CI Server”
Jenkins implementations are typically focused on the technical part of your application delivery: building code, spinning up servers, executing simple deployment patterns, running tests, and so on. And if you’re lucky enough to be working in an environment where that’s all you need to do––at a relatively small scale––Jenkins will probably work just fine.
You will find XebiaLabs Release Orchestration particularly valuable in combination with Jenkins when you consider the “process-level” requirements of your Continuous Delivery pipeline: