Intro to Continuous Integration
Download as PPTX, PDF0 likes117 views
The document discusses continuous integration (CI) as a practice for integrating tested code daily to avoid issues like undetected bugs and production outages. It outlines the steps and tools involved in implementing CI, specifically mentioning GitHub CI server and CircleCI for deployment. It also highlights the importance of maintaining small code changes for quality assurance and effective testing.
Related topics:1 of 20
Download to read offline
Intro to Continuous Integration
- 3. Continuous Integration The practice of integrating tested code every day, automatically. -- Grady Booch *This is not a quote
- 5. #1 – Undetected Bugs (fear of change) • Production Outage • Butterfly effect • Angry users • Page slowness • Security holes • Distorted web page • Mobile incompatibility • Typos • Usability impact
- 8. What’s in v1.2? When is the feature due?
- 10. The Solution
- 11. • A working piece of code • Tested (manually + unit) • Not production ready • Small enough to ensure quality • Small enough to code review
- 13. CI Server • Compile • Execute Unit Tests • Test Database Integration • Perform Code Inspection • Deploy to Staging/QA • Keep record of “who did what?”
- 14. Some Tools out there
- 16. Demo time
- 17. Demo 1. Fork this: https://github.com/tal-moshayov/angular- seed 2. Fetch: git clone https://github.com/…/angular-seed 3. Test: npm run test-single-run 4. Run: npm start & open http://localhost:8000 5. Sign up with CircleCI and connect to GitHub Now let’s write the circle script:
- 18. Demo - CircleCI Test phase Deploy phase Build phase
- 19. Demo - CircleCI
- 20. FIN