continuous delivery with jenkins enterprise and ibm urbancode deploy

©2015 CloudBees, Inc. and IBM All Rights Reserved 1 ©2015 CloudBees, Inc. and IBM All Rights Reserved

Continuous Delivery with Jenkins

Enterprise and UrbanCode Deploy

Kohsuke Kawaguchi / CTO, CloudBees, Inc.

- [email protected] / @kohsukekawa

Eric Minick / Release Automation Product Manager, IBM

- [email protected] / @EricMinick

©2015 CloudBees, Inc. and IBM All Rights Reserved 2

Ground Rules

We’re all friends today!

Do you also compete in some circumstances? Do you integrate with the other’s competitors? Don’t you overlap in some way?

Valid questions we won’t discuss today


Infrastructure as Code

IaaS

PaaS

Automated Testing


Introducing Jenkins

©2010 CloudBees, Inc. All Rights Reserved


Extensible through 950+ plugins


0

500,000

1,000,000

1,500,000

2,000,000

2,500,000

3,000,000

3,500,000

4,000,000

Number of Jobs


Jenkins is everywhere


Copyright Google


Dockercon keynote


Copyright HBO


Even on a TV show


Traceability with Puppet/Chef

Dev

Ops

Traceability to the checkin Traceability to the deployment Traceability to the machine


Host that runs Docker

Jenkins + Docker = elastic build slave


Jenkins + Git = validated merge

• No more broken builds

• Improve developer efficiency

• Run tests more efficiently

upstream repo

gate repo


Jenkins & UrbanCode Deploy

• Push artifacts as new component version

urbancode deploy

v1.0.${BUILD_NUMBER}



• Trigger a process

urbancode deploy



• Lots of options to compose them

– single linear pipeline

– build promotion

• “thumbs up” based approach

• For example,

– Build, unit test, and deploy automatically

– Allow someone to put “a thumb up” on a build

– Automatically trigger deployment to UAT

– Ops can use UC Deploy to push it into prod


Build Promotion Illustration

Foo #5



Foo #5

FooTest #10



Foo #5

FooTest #10

BarTest #16



Foo #5

FooTest #10

BarTest #16

FooIntTest #9



Foo #5

FooTest #10

BarTest #16

FooIntTest #9

FooIntTest #10



Foo #5

FooTest #10

BarTest #16

FooIntTest #9

FooIntTest #10

Deploy #19


Containerized components


rspec-puppet test as PR validation


On-server testing with serverspec


r10k + puppet enterprise

Every branch automatically becomes environment


Two key branches & environments

‘staging’ branch

‘production’ branch


Workflow as code

node {

workspace {

git(url: ‘http://server/myapp.git’)

for ( i in 0..<10)

sh ‘mvn test –Dsuite=${i}’

}

}


More reasons why we like buildflow

• Rich control flow

• Rich abstractions

• Meaningful diff


Leap: one place for everything

• Not just calling other jobs

• Check out source code

• Fork processes

• Archive artifacts

• …


Leap: resilience

Build #153


Leap: resilience

Build #153 Build #153


Leap: checkpointing


As the usage grows:

Jenkins Enterprise by CloudBees

Professional support

High availability

Large installations

Security

Optimized utilization


Conclusions

• More and more integrations

• Non-prescriptive approach for the win

• Many successful CD pipelines with Jenkins

• Workflow ties them all together


“Classic” CD

build dev

test

system

test UAT sign-off staging prod


Enterprise Challenges

?

Complex Systems have many parts

many specialists and teams too

Image credit: https://www.flickr.com/photos/billward/155440416


Composite apps: many tiers & components



An Application might have

dozens of components



An Application might have

dozens of components

Delivered by Different Teams



Which build does “Login” test?


Build pipelines in composite applications

build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system


build dev

test

system



These people deploy one build at a time to prod

88% Deploy More than one build to production a time

√

√

√


Key “Gotchas”

• Related stuff is deployed / released together

• Some of it isn’t built

• Some of it is incremental Man… Databases,

content, middleware config are a pain


The Plan!

• Continuous Delivery Overview

• Jenkins is awesome

• What’s new in Enterprise Jenkins

• Deployment “gotchas” for CD

• UrbanCode Deploy is awesome

• What’s new in UrbanCode Deploy

• The integrated scenario


Intuitive and Scalable Model Driven Deployment

Composite Applications

Components

Re-usable Processes Environment

Management

SIT

PROD

The “What”

The “How”

The “Where”

Deployment

Automation


Components:

- Individual deployable projects

Application:

- A complete collection of components

- Describes inter-component dependencies

Applications are made of Components


Application Deployments made of Component

Deployments Application Process

- Orchestrate deployment of many components

- Represents deploy-time dependencies

Component Process

- How to deploy a thing to a target

Drag-and-Drop Workflow Designer

Processes are Versioned with Change Logs

Create Custom Steps


Snapshots promote tested versions ….

• Manage a set of tested component versions as a single unit

• Guarantee the validated versions of related components are

deployed together

• Ease of promoting applications between environments

1

1

2

3

UAT Stage PROD

Promote Promote

Web

Mid. Code

Mid. Config

DB

Snapshot


The Plan!









What’s new

93


Lots of new integrations

94

developer.ibm.com / urbancode / plugins


Dev/Test with Hybrid Cloud

95

Off

-Pre

m

On

-Pre

m

Image Registry

IBM Bluemix

IBM UrbanCode Deploy PROD STAGING


The Plan!









Plugin to push files / trigger deploys

Jenkins can Easily: • Tell UC Deploy about

new versions • Trigger deployments to

dev and test environments

Use Workflow to promote through independent testing environments.


On build completion, Jenkins

publishes the latest artifacts

to UrbanCode Deploy and

deployed to a development

or SIT environment.

After deployment,

automated tests are started.

If they pass, we mark the

tested versions as such.

Before any

deployments to

production, manual

approvals are

required.

The exact combination of

component versions which

passed tests is captured in a

snapshot.

Putting it all together – Continuous Delivery

The “What”

The “Where”

The “How”

©2015 CloudBees, Inc. and IBM All Rights Reserved 99 ©2015 CloudBees, Inc. and IBM All Rights Reserved

Questions?

Kohsuke Kawaguchi / CTO, CloudBees, Inc.

- [email protected] / @kohsukekawa

Eric Minick / Release Automation Product Manager, IBM

- [email protected] / @EricMinick

continuous delivery with jenkins enterprise and ibm urbancode deploy

Software