Continuous Integration and Delivery

A talk on Continous Integration, deployment and delivery presented at GDG cloud Nairobi on October 19, 2017.

Transcript

1. Continuous {Integration, Deployment, Delivery}
2. Challenges • Software projects become large and complex as they grow
3. Challenges • Software projects become large and complex as they grow • More members join the team and some are often remote.
4. Challenges • Software projects become large and complex as they grow • More members join the team and some are often remote. • Tight delivery schedules
5. Challenges • Software projects become large and complex as they grow • More members join the team and some are often remote. • Tight delivery schedules • Frequent need for updates, fixes and new features.
6. Continuous Integration • A software Development practice where members of a team integrate their work frequently
7. Continuous Integration • A software Development practice where members of a team integrate their work frequently • Integration can be done by any member anytime but at least once in a day leading to multiple integrations in a day.
8. Continuous Integration • A software Development practice where members of a team integrate their work frequently • Integration can be done by any member anytime but at least once in a day leading to multiple integrations in a day. • Each integration is verified by an automated build to detect any integration errors before the integration is done.
10. Principles • Keep all files in Version control
11. Principles • Keep all files in Version control • Integrate at least once a day
12. Principles • Keep all files in Version control • Integrate at least once a day • Every integration should trigger an automatic build
13. Principles • Keep all files in Version control • Integrate at least once a day • Every integration should trigger an automatic build • Run tests after every integration.
14. Key Concepts of CI • Source Control
15. Key Concepts of CI • Source Control • Tests
16. Key Concepts of CI • Source Control • Tests • Automated Builds
17. Key Concepts of CI • Source Control • Tests • Automated Builds • Automated Deployments
18. Version Control Git Mercurial Please use the above. Actually just use git!!! Outdated stuff - CVS, Subversion, Visual Source Safe
19. Tests For good CI we need good tests setup. Tests ensure we do not break existing code when we introduce new features
20. Tests For good CI we need good tests setup. Tests ensure we do not break existing code when we introduce new features • Unit Tests - A unit test determines the correctness of an individual component in a large codebase. A unit test should work in isolation from other tests. Unit tests are atomic.
21. Tests For good CI we need good tests setup. Tests ensure we do not break existing code when we introduce new features • Unit Tests - A unit test determines the correctness of an individual component in a large codebase. A unit test should work in isolation from other tests. Unit tests are atomic. • Integration Tests - Integration tests determine the correctness of the codebase as a whole when all the individual components are brought together.
22. Popular CI Tools • Jenkins - Most popular CI tool written in Java. Has plenty of plugins
23. Popular CI Tools • Jenkins - Most popular CI tool written in Java. Has plenty of plugins • Go - CD tool built by thoughtworks
24. Popular CI Tools • Jenkins - Most popular CI tool written in Java. Has plenty of plugins • Go - CD tool built by thoughtworks • Bamboo - CI tool from Atlassian.
25. Popular CI Tools • Jenkins - Most popular CI tool written in Java. Has plenty of plugins • Go - CD tool built by thoughtworks • Bamboo - CI tool from Atlassian. • Strider - Open Source CI tool written in Nodejs
26. Popular CI Tools • Jenkins - Most popular CI tool written in Java. Has plenty of plugins • Go - CD tool built by thoughtworks • Bamboo - CI tool from Atlassian. • Strider - Open Source CI tool written in Nodejs • BuildBot - Open Source Python CI
27. Popular CI Tools • Jenkins - Most popular CI tool written in Java. Has plenty of plugins • Go - CD tool built by thoughtworks • Bamboo - CI tool from Atlassian. • Strider - Open Source CI tool written in Nodejs • BuildBot - Open Source Python CI • TeamCity - Another free self-hosted CD platform by JetBrains
28. CI as a Service • CodeShip
29. CI as a Service • CodeShip • Travis CI
30. CI as a Service • CodeShip • Travis CI • Circle CI
31. CI as a Service • CodeShip • Travis CI • Circle CI • Gitlab CI
32. CI as a Service • CodeShip • Travis CI • Circle CI • Gitlab CI • BuildKite
33. CI as a Service • CodeShip • Travis CI • Circle CI • Gitlab CI • BuildKite • Visual Studio Team Services
34. Continuous Deployment Continuous deployment builds on Continuous Integration to continually deploy new features as they are added.
37. Continuous Delivery • Builds on top of Continous Integration and Continuous Deployment.
38. Continuous Delivery • Builds on top of Continous Integration and Continuous Deployment. • Approach where teams release software in short cycles.
39. Continuous Delivery • Builds on top of Continous Integration and Continuous Deployment. • Approach where teams release software in short cycles. • Makes it possible to continuously adapt software to users needs.
40. Continuous Delivery • Builds on top of Continous Integration and Continuous Deployment. • Approach where teams release software in short cycles. • Makes it possible to continuously adapt software to users needs. • Enables organisations to release frequently and get quick feedback
41. Benefits of CI/CD • Faster reaction times
42. Benefits of CI/CD • Faster reaction times • Reduced risks
43. Benefits of CI/CD • Faster reaction times • Reduced risks • Reduced deployment times
44. Benefits of CI/CD • Faster reaction times • Reduced risks • Reduced deployment times • Automation saves time and money
45. @jmwai