Jenkins CI + XebiaLabs for Release Orchestration: A Recipe for Continuous Delivery Success

JenkinsCI+XebiaLabsforReleaseOrchestrationA Recipe for CD Success September 2016

2 Copyright2016.Confiden4al–Distribu4onprohibitedwithoutpermission

Housekeeping

▪ This webinar is being recorded

▪ Links to the slides and the recording will be made available after the presentation

▪ You can post questions via the GoToWebinar Control Panel


Meet Your Presenter

Tim Buntel VP of Products, XebiaLabs

@tbuntel


Agenda

4

•  A trip down (CD tools) memory lane •  Release Pipeline Orchestration •  Jenkins + XL Release •  Questions & Discussion


ABriefHistory

DevOps=PeopleProcessesProducts


WhyAutomate?

▪  Consistent ▪  Repeatable ▪  Auditable ▪  Fast ▪  Scalable


Fromthedawnofprogramming

ByArnoldReinhold-Itookthispictureofanar4factinmypossession.Thecardwascreatedinthelate1960sorearly1970sandhasnocopyrightno4ce.,CCBY-SA2.5,hNps://commons.wikimedia.org/w/index.php?curid=775153


Compiling&Debugging

UW Special Collection, 79-0009-207. https://cs.uwaterloo.ca/40th/Chronology/printable.shtml


TestingTools

ByBundesarchiv,B145Bild-F038812-0014/Schaack,Lothar/CC-BY-SA3.0,CCBY-SA3.0de,hNps://commons.wikimedia.org/w/index.php?curid=5455799


BuildAutomation

1977-MAKE 2000-AnthNps://commons.wikimedia.org/wiki/File:Radioshack_TRS80-IMG_7206.jpg#/media/File:Radioshack_TRS80-IMG_7206.jpg


1994


ContinuousIntegration

ByGrady_Booch,_CHM_2011_2.jpg:vonguardfromOakland,Nmibiaderiva4vework:YMS-ThisfilewasderivedfromGradyBooch,CHM20112.jpg:,CCBY-SA2.0,hNps://commons.wikimedia.org/w/index.php?curid=26328892


CITools

Hudson2005(Jenkins2012)

CruiseControl2001ByTheoriginaluploaderwasFaisal.akeelatEnglishWikipedia-Transferredfromen.wikipediatoCommonsbyLegoktmusingCommonsHelper.,CCBY2.5,hNps://commons.wikimedia.org/w/index.php?curid=4519254


Configuration&DeploymentManagement

A B

•  Files•  Configura4on•  Etc.


Configuration&DeploymentManagement

A B

•  Files•  Configura4on•  Etc.

2005

2009

2009


AnAutomatedPipeline

•  Build•  Integrate•  Test•  Provision•  Deploy•  Operate

•  Security•  Compliance•  Accessibility•  Etc.

AndlotssBllmanual…


Somanyseparatetools!

Provision

Plan Code Build Test Release Operate

mainframe

Dev Test Prod


Achaoticreleaseprocess

▪ Copious spreadsheets, Word docs and emails, often with everyone working from different versions

▪ Daily status meetings, often early in the morning

▪ Frenzied phone calls to get the latest status and track down issues

▪ No visibility across the business

▪ No good way to capture changes for audit purposes

!


Needsomethingtobringitalltogether

By -tjgtheatre.org,CCBY-SA3.0,hNps://commons.wikimedia.org/w/index.php?curid=26365651


▪  Orchestrate ▪  Automate ▪  Manage ▪  Capture metrics and logs ▪  Give real-time status ▪  Show problems in early stages so you can fix them

What,exactly,isReleaseOrchestration?


Useexistingtools?CI

Provisioning

1.  Scrip4ngdoesn’tscaleandisdifficulttomaintain

2.  Repurposedtechnicaltoolslackvisualiza4on,intelligenceandrepor4ngcapabili4es

3.  Technicaltoolsdon’tworkacrossthebusiness

4.  Typicallylackenterprise-levelcomplianceandsecurityfeatures


JenkinsisgreatforCI

ACIServerautomatestaskstoverifythateachdeveloper’scodecheck-indoesn’tbreaksomethingelseintheproject.•  runningbuilds•  invokingtests•  triggeringdeploymentautoma4ontools•  andmanyotherdeveloper-centric

ac4vi4esJenkinsisgreatforCI.


V I S I B I L I T Y

AUTOMATION

CONTROL

§  Con4nuousDeliveryandDevOpspioneer,authorityandtechnologyleader

§  GlobalteaminUS,Europe&APAC

§  Consistentlyrecognizedbyleadingindustryanalysts

Connec4ngthedotsforCon4nuousDeliveryatenterprisescale

AboutXebiaLabs

G l o b a l L e a d e r s D e l i v e r S o i w a r e w i t h X e b i a L a b s


Plan,automateandanalyzetheen4resoiwarereleasepipeline

Alwaysknowthestatusofautomatedandmanualstepsacrossthereleasepipeline

Iden4fyboNlenecks,reduceerrorsandlowertheriskofreleasefailures

Managethemostadvancedreleasepipelineswithease

Orchestrate,automate+viewreleasepipelines

✔End-to-endReleaseOrchestra4on

✔Pipelineautoma4on

✔Pipelinedashboards+analy4cs

✔Pipelinetemplates

✔Automatedandmanualtasks

✔Agentless

✔Plug-ins

✔Enterpriseauditability+controls

✔Easytoimplement+use

Includeexis,ngtoolsinreleaseorchestra,onSCM,CI,ALM,ChangeManagement,TestTools,Provisioning✔

StandardizedReleaseProcess

End-to-endPipelineVisibility

ReducedRisk+Errors

Foralltypesofenterpriseapplica,onsLegacy,mainframe,client-server,cloud,mobile,micro-services,hybrid✔ AgentlessArchitectureForsecureandeasyimplementa,on✔


Provision

Plan Code Build Test Release Operate

Dev Test Prod

mainframe

Doingwhattheydobest


3waystointegrate

XLReleaseFirst

JenkinsFirst

HybridPipeline

XLRReleasepluginforJenkins

JenkinspluginforXLRRelease


XLReleaseFirst


JenkinsFirst


JenkinsFirst


HybridPipeline


HybridPipeline


Summary

1. Continuous Delivery Doesn’t Scale Without Release Orchestration

2. XL Release for Release Orchestration works beautifully with Jenkins for CI

▪ Enterprises that implement release orchestration often reduce the time to release software from months down to days, or even hours.

▪ They frequently release software 10-20X more quickly just a few months after implementing release orchestration.

▪ Software quality improves dramatically, with enterprises moving from multiple production incidents with every release down to only a few incidents a year

Outcomes:

Q&A