Constinuous Integration
- 1. CI/CD Continuous Integration / Continuous Delivery
- 2. Gabriel Araujo ● I’m not an expert ● Full-Stack Web Developer ● Wordy Curious guy ● Fascinated by automation and computer-assisted tasks ● Work Experience ○ Jenkins ○ TeamCity ○ Travis ○ VSTS ○ Gitlab CI ○ Codeship ○ ...
- 3. What is Continuous Integration?
- 4. The practice of regularly integrating code changes into the mainline.
- 6. “Continuously is more often than you think.” - Mike Roberts
- 7. Why teams are doing it?
- 10. Ready to deploy at any time.
- 13. Why teams are not doing it?
- 15. Too much change.
- 19. Extreme Programming Explained by Kent Beck (1999) ● Sit Together ● Whole Team ● Informative Workspace ● Energized Work ● Pair Programming ● Stories ● Weekly Cycle ● Quarterly Cycle ● Slack ● Ten-Minute Build ● Continuous Integration ● Test-First Programming ● Incremental Design
- 20. Commit Code Frequently ● Integrate early and often ○ Integration = Communication ● Avoid late integration ○ long-lived branches ○ Branch-heavy workflow (e.g., gitflow) ○ Time-consuming ○ Prevent developers from using latest changes ● Make small changes ○ Break down a larger task ○ Feature flags ● Commit after each task ● Up to date mainline ● Conflicts reduced ● Smaller PRs ● Better code review
- 21. Automated Builds ● Complicated process but predictable ○ Reproducible on any environment ● From zero to hero with a single command ● Keep the build fast ○ Build what’s needed ○ Lightweight builds (private builds) ○ Caching strategies ● Run automated tests and inspection ○ Generate reports ○ Visualize trends ● Fix broken builds immediately
- 22. “Crucially, if the build fails, the development team stops whatever they are doing and fixes the problem immediately” - Jez Humble and David Farley
- 23. Criticism ● Builds get broken often ● Unable to fix errors in time ● Code is already on master ● Build flags are ignored
- 24. Continuous Integration vs Continuous Delivery vs Continuous Deployment
- 25. Code Build Integrate Test Release Deploy Continuous Integration Continuous Delivery Continuous Deployment
- 26. Build and Test Automated System Dev Dev Dev Dev Dev Production Feat 346 Feat 45 Testing Staging
- 27. Services and tools ● Jenkins ● Bamboo ● Bitbucket Pipelines ● TeamCity ● VSTS ● Codeship ● Travis CI ● CircleCI ● GO ● Gitlab CI ● Github Actions ● Buildbot ● CruiseControl ● AppVeyor ● Drone.io ● ...
- 28. Hands on And a little bit of code
- 29. Gitlab CI Features ● Configuration as code (yaml) ● Your own distributed isolated runners ● Multi-stage and parallel jobs ● Manual deploy gates ● Artifacts storage ● Built-in registry ● Docker, shell, support (main) ● Environments ● Review Apps (preview) ● Caching configs ● Triggers ○ Push ○ Branches, tags (regex) ○ Other pipeline ○ Schedules ○ API ○ Manual (web) ○ Merge requests ○ Chats
- 31. Code pushed to gitlab unit tests integration testsbuild deploy
- 32. feature/* develop stage Code pushed to gitlab lint TS lint SCSS unit tests build build build deploy deploy deploy destroy ui tests
- 33. feature/* master tag version Code pushed to gitlab lint TS lint SCSS unit tests build build build deploy deploy deploy destroy ui tests
- 34. Thanks! Contact me: Invillia 151 Padre Duarte Araraquara, SP 14800-360 contato@gabrielaraujo.dev gabrielaraujo.dev
- 35. References ● Continuous Integration - What's the point? ● Why Continuous Integration Doesn’t Work ● Software Configuration Management Patterns: Effective Teamwork, Practical Integration ● What is a Continuous Integration and Delivery Pipeline, and Why Is It Important? ● Continuous Integration: Improving Software Quality and Reducing Risk