Continuous Integration (CI) involves integrating code changes frequently from developers, verifying that the integrated code works with automated builds and tests. This allows problems to be detected early. With CI, developers commit code changes to a source repository. A CI server then checks out the changes, builds the code, and runs tests to catch any errors. The server notifies the team of build failures so issues can be addressed quickly. Metrics from CI builds provide insight into the health of the project.

1. Continuous Integration (CI)

2. Motivation

5. Definition

7. Demonstration

8. Continuous Integration Server Source Repository Developers Solution: continually integrate and test throughout the project

9. Developers check out code into their private workspaces

10. Developers work on functionality and validate it by running unit tests and local build

11. Developer update code to avoid conflicts

12. Developers work on functionality and validate it by running unit tests and local build

13. When done, they commit changes to the repository

14. The CI server monitors the repository and checks out changes when they occur

15. The CI server builds the system and runs unit and integration tests

16. The CI server releases deployable artefacts for QA testing

17. The CI server assigns a build label to the version of the code that it just built

18. The CI server informs the team of the successful build and generates useful metrics

19. If the build or tests fail, the CI server alerts the team

20. The team fix the issue at the earliest opportunity

21. Continually integrate and test throughout the project

22. Metrics

23. Metrics generated by the CI server can be a useful indication of project “health”

24. Metrics generated by the CI server can be a useful indication of project “health” (cont.)

25. Reminder

32. Practices of Continuous Integration

41. Conclusion

47. ? Q & A