16
Jenkins + Docker Continuous Improvement

Jenkins + Docker = Continuous Improvement

Embed Size (px)

Citation preview

Jenkins + DockerContinuous Improvement

About MeDirector @CloudBees @udaypal @linkedin.com/in/udaypal @udaypal.com @bayareajam

CloudBees

• Jenkins Enterprise Company

• Kohsuke CTO / Core committers

• Red Hat / Linux = CloudBees / Jenkins

• Subscriptions, Services, Training, Enterprise features

• Growing / Hiring

FasterCheaper

Better

Expensive

Poor

Late

Kaizen in Action

Look in the mirror• How efficient is your SDLC?

• Is there room for improvement?

• How often do you address the gaps?

• How quickly can you make a change ?

• Is the system designed to support quick changes?

• What’s your incentive to make a change?

Jenkins + Docker• Cheaper

• Better Utilization

• Ease of use

• Faster

• Provisioning

• Integrated with Jenkins = Faster CD pipelines

• Better (YMMV and you control it)

• Faster feedback

• Flexible - Change is easier

Use Cases• Manage Docker registry credentials centrally

• Standardized environments

• Support snow flake environments

• Modular CD pipelines using Workflow

• Container Dependency

• Tracking containers

Demo