Transition from CI to CD
-
Upload
nanjekye-joannah -
Category
Technology
-
view
269 -
download
0
Transcript of Transition from CI to CD
![Page 1: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/1.jpg)
The Transition from Continuous Integration to continuous Delivery
Joannah [email protected]
@JoannahNanjekyeGeek night kampala
![Page 2: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/2.jpg)
● Joannah Nanjekye● Programmer , Fintech Uganda Limited● .Net and Ruby.● Interests
systems programming
About me
![Page 3: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/3.jpg)
Outline
● Overview of CI● Continuous delivery● Demo
![Page 4: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/4.jpg)
what is continous integrationContinuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day
http://www.martinfowler.com/articles/continuousIntegration.html
![Page 5: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/5.jpg)
A Typical CI workflow
![Page 6: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/6.jpg)
The last mile to a release
last mile
![Page 7: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/7.jpg)
The last mile
“It is hard enough for software developers to write code that works on their machine.But even when thats done,there is a long journey from there to software that is producing value since software only produces value when its in production.”
Martin Fowler
![Page 8: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/8.jpg)
Release management Antipatterns
● Manual deployments● Wait until development is done to release.● Manual configuration management.
![Page 9: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/9.jpg)
![Page 10: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/10.jpg)
There is need for repeatable,reliable and reusable way of ensuring reliable releases;
![Page 11: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/11.jpg)
Continuous Delivery
![Page 12: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/12.jpg)
...a set of practices to software delivery that aims at building software so that it is in a state where it could be in production or is releasable at any time ...
What is continous delivery..
![Page 13: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/13.jpg)
Goal
● High Quality releases● Low cycle time
![Page 14: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/14.jpg)
Continuous delivery setup
![Page 15: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/15.jpg)
You are doing CD when….
● Your software is deployable throughout its lifecycle
● Team Priority is having deployable software over working on new features
● Anybody can get fast, automated feedback on the production readiness of their systems any time somebody
makes a change to them
● You can perform push-button deployments of any version of the software to any environment on demand
http://martinfowler.com/bliki/ContinuousDelivery.html
![Page 16: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/16.jpg)
Continous what????
![Page 17: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/17.jpg)
what is required to do CD● Automation of the delivery process.
○ Automated testing○ Continuous integration○ Automated deployment
● The ‘DevOps’ culture of delivery.
![Page 18: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/18.jpg)
Benefits of Continuous delivery
● Making release a non-issue.● Faster Feedback .● Believable progress.● Accelerated time to market.
![Page 19: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/19.jpg)
challenges
● Automated tests● Developer training● Incremental releases are complicated.
![Page 20: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/20.jpg)
Demo
![Page 21: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/21.jpg)
![Page 22: Transition from CI to CD](https://reader031.fdocuments.us/reader031/viewer/2022030302/587cd3ac1a28abff0b8b46dd/html5/thumbnails/22.jpg)
Thank you