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...
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 ...
Configuration Management
Build Pipeline
Guarantees the production readiness
Makes release a risk-free automated affair
Tie release with business de...
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 ni...
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...
Thanks !!
Questions?
http://bit.ly/JenkinsCDWorkshop
@leenasn @akshaykashain continuousdelivery.in
Continuous delivery using jenkins
Continuous delivery using jenkins
Continuous delivery using jenkins
Continuous delivery using jenkins
Continuous delivery using jenkins
Upcoming SlideShare
Loading in...5
×

Continuous delivery using jenkins

788
-1

Published on

This is the slides of the presentation that we used for Continuous Delivery using Jenkins

Published in: Engineering, Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
788
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
20
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Continuous delivery using jenkins

  1. 1. Continuous Delivery using Jenkins
  2. 2. Why Continuous Delivery is important Intro to Jenkins and Build Pipeline Setup Takeaways
  3. 3. Water Scrum Fall
  4. 4. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software First Principle of Agile Manifesto
  5. 5. Done = Released
  6. 6. Fast, automated feedback on the correctness of your application every time there is a change to code Continuous Integration
  7. 7. Continuous Integration in Action
  8. 8. Business Engineering Team
  9. 9. Continuous Delivery Fast, automated feedback on the production readiness of your application every time there is a change — to code, infrastructure,or configuration.
  10. 10. Configuration Management
  11. 11. Build Pipeline Guarantees the production readiness Makes release a risk-free automated affair Tie release with business decisions
  12. 12. Build Pipeline in Action
  13. 13. Feature Branches
  14. 14. Mainline Development
  15. 15. Summary Everyone is responsible for Release Build Quality In Continuous Improvement
  16. 16. 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
  17. 17. 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
  18. 18. Thanks !! Questions? http://bit.ly/JenkinsCDWorkshop @leenasn @akshaykashain continuousdelivery.in
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×