Continuous Delivery using

Jenkins

Why Continuous Delivery is important

Intro to Jenkins and Build Pipeline Setup

Takeaways

Water Scrum Fall

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

First Principle of Agile Manifesto

Done = Released

Fast, automated feedback on the correctness of your application every time there is a change to code

Continuous Integration

Continuous Integration in Action

Business

Engineering Team

Continuous Delivery

Fast, automated feedback on the production readiness of your application every time there is a change — to code, infrastructure,or configuration.

Configuration Management

Build Pipeline

Guarantees the production readiness

Makes release a risk-free automated affair

Tie release with business decisions

Build Pipeline in Action

Feature Branches

Mainline Development

Summary

Everyone is responsible for Release

Build Quality In

Continuous Improvement

If humans start doing those repetitive tasks which computers are designed to do, all the computers get together late at night and laugh at you

Neal Ford

Next Steps

How long would it take you to deploy a change that involves just one single line of code?

Can this be done on a repeatable, reliable basis?

Mary and Tom Poppendieck

Thanks !!

Questions?

http://bit.ly/JenkinsCDWorkshop

@leenasn @akshaykashain continuousdelivery.in