Why don’t I just use Jenkins or another CI server to build and manage my Continuous Delivery pipelines?

Simple. It’s the wrong tool for the job.

You need to take the view that Continuous Delivery is not just “a few more jobs in my CI server.”

As Etsy’s principal engineer puts it: “[Our] job is keeping the company in business, g*d d*** it.”

Since Continuous Delivery is an end-to-end discussion, we need tooling that can handle the full scope...and handle it right now. CD is about continuous improvement, not just about orchestrating a finished process. This is where Jenkins and other CI servers today fall short, and what a Continuous Delivery Management tool such as XL Release is designed to do:

Jenkins and other
CI Servers
XL Release and
other CDM tools

Can my tools address the full Dev to Production process?
Dev-to-QA != CD

Fosters team collaboration, with a UI interface that is friendly and usable across all teams

NY

Supports manual and automated tasks

NY

Easy to use for Dev, QA, DBAs, release managers etc., not just automation gurus

NY

Views relevant to job function (release calendar, release pipeline, release tasks)

NY

Integrates smoothly with ALM, change/release management and other process tools

NY

Supports multiple pipelines, release trains, dependencies and other complex delivery patterns, not just single pipelines

NY

Can I get started quickly and use my tools to gather the data needed to improve?
CD is about continuous improvement

Define your end-to-end process in 30 min, not 30 hours

NY

Tweak running pipelines to understand where “reality gets in the way of the plan”

NY

Enables data-driven improvement: provides metrics and analytics to speed up your pipeline

NY

Comprehensive visual dashboards and reports

NY

Can I scale my tools to multiple teams and enterprise usage?

Scales to hundreds of users and pipelines in a highly available setup

NY

Security model appropriate for enterprise CD: accessible to anyone in the enterprise, with controls

NY

Audit trail for all changes to pipeline definitions and running releases

NY

Integrations with all the types of tools encountered from Dev to Prod - not just build and test tools

NY

Easy to create custom extensions without learning a complex plugin API: no proprietary language, no scripts, no need for Groovy DSLs

NY

Simplified maintenance - no unpredictable upgrades, incompatible extensions etc.

NY

So...are you saying I should get rid of Jenkins/Bamboo/TFS/TeamCity etc.?


Not at all! We’re saying you should consider a purpose-built tool for Continuous Delivery Management - one that is actually designed for CD and gives you the right platform to improve your end-to-end process of getting code out to your users. Try it and see how easy it is: Download XL Release now


More Information: