Downloaded 30 times
Uploaded byRodrigo Russo
QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
The document discusses principles of continuous integration including version control, automation, and testing. It describes a basic continuous integration/continuous delivery (CI/CD) pipeline with stages for committing code, compiling, testing, and deploying to environments like acceptance, capacity, and production. Jenkins is presented as a tool for implementing CI/CD pipelines through automated jobs that can pull code, build, test, analyze, and deploy software.
More Related Content
Similar to QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration
- 1. CONTINUOUS INTEGRATION FabricioLeotti | Rodrigo Russo
- 2.
- 3. Princípios básicos • Controle de versão
- 4. Princípios básicos • Controle de versão • Prepare para a automação
- 5. Princípios básicos • Controle de versão • Prepare para a automação • Faça, meça, corrija
- 6.
- 7. Branching strategy • Master branch
- 8. Branching strategy • Master branch
- 9. Branching strategy • Master branch
- 10. Branching strategy • Master branch
- 11. Branching strategy • Master branch
- 12. Branching strategy • Master branch
- 13. Branching strategy • Master branch
- 14. Branching strategy • Master branch
- 15. Branching strategy • Master branch
- 16. Branching strategy • Master branch
- 17. Branching strategy • HoKix
- 18. Branching strategy • HoKix
- 19. Branching strategy • HoKix
- 20. Branching strategy • HoKix
- 21. Branching strategy • HoKix
- 22. Branching strategy • HoKix
- 23. Branching strategy • HoKix
- 24. Branching strategy • HoKix
- 25. Branching strategy • HoKix
- 26. Branching strategy • HoKix
- 27. Branching strategy • HoKix
- 28. Branching strategy • HoKix
- 29. Branching strategy • HoKix
- 30.
- 31. CI/CD Pipeline ABasic Deployment Pipeline Figure 5.4 shows a typical deployment pipeline and captures the essence of the approach. Of course, a real pipeline will reflect your project’s actual process for delivering software. Artifact repository Source code Commit stage Compile Commit tests Assemble Code analysis reports binaries metadata Acceptance stage Configure environment Deploy binaries Smoke test Acceptance tests Capacity stage Configure environment Deploy binaries Smoke test Run capacity tests UAT Configure environment Deploy binaries Smoke test Env & app config reports metadatabinaries Production Configure environment Deploy binaries Smoke test Env & app config binaries reports metadata Operations perform push-button releases Testers Self-service deploymentsDevelopers See code metrics and test failures Version control Figure 5.4 Basic deployment pipeline
- 32. Jenkins Pipeline Code pull Build & Unit Tes1ng Build & Promote Package Sta1c Analysis Commit Stage <Environment> Deployment <Environment> Smoke Test <Environment> Integra1on Test <Environment> Acceptance Test Acceptance Stage <Environment> Load Test <Environment> Performance Test Capacity Stage Deploy Binaries Configure Environment Produc1on Smoke Test
- 33.
- 34. Jenkins Pipeline • Jenkins jobs
- 35. Jenkins Pipeline • Jenkins jobs
- 36. Jenkins Pipeline • Jenkins jobs
- 37. Jenkins Pipeline • Jenkins jobs
- 38. Jenkins Pipeline • Jenkins jobs
- 39. Jenkins Pipeline • Jenkins jobs
- 40. Jenkins Pipeline • Jenkins jobs
- 41. Jenkins Pipeline • Jenkins jobs
- 42. Jenkins Pipeline • Jenkins jobs
- 43. Jenkins Pipeline • Jenkins jobs
- 44. Jenkins Pipeline • Jenkins jobs
- 45. Jenkins Pipeline • Jenkins jobs
- 46. Jenkins Pipeline • Jenkins jobs
- 47.