Continuous Integration
How to Do it?
1. Developers check out code into their private workspace
2. When done, commit changes to the repository
3. CI server monitors the repository & check out changes when they occur
4. CI server builds the system & runs, unit & integration tests
5. CI server releases deployable artefacts for testing
6. CI server assigns a build label to the version of the code it just built.
7. CI server informs the team of the successful build
8. If the build or tests fails, CI server alert the team
9. Team fix issue at their earliest opportunity.
Team Responsibilities in CI?
1. Check-In frequently
2. Don’t check-in broken code
3. Don’t check-in un-tested code
4. Don’t check-in, when build is broken
5. Don’t go home after checking-in, until system builds
Continuous Integration:
- Requires developers to integrate code into shared repository several times a day.
- Each check-in is than verified by automated build
CI Benefits:
1. Not long and tense integration
2. Increase visibility which enable greater communication
3. Catch issue fast and nip them in the bud.
4. Spend less time debugging and more time addition new features
5. Proceed in the confidence, you are building on solid foundation
6. Stop waiting to find out, if your code is going to work
7. Reduce Integration problems, allowing you to deliver software more rapidly.
CI Practises:
1. Maintain a single source repository
2. Automate the build
3. Make sure build self-testing
4. Every commit should built on an integration machine
5. Keep the build fast
6. Test in a clone of the production environment
7. Make it easy for everyone to get the latest executable.
8. Everyone can see what is happening
9. Automate deployment