In software development, Continuous Integration is the practice of merging all developers’ working code to the main or head branch several times a day. This makes other practices from Automated Builds -> Continuous Delivery possible. Note: contrary to popular belief, Continuous Integration is the habit of frequent checkins and not the build automation. The automated builds are the supporting tools that make CI practical.
Resource Links:
- It’s Not CI, It’s Just CI Theatre
- Keep your code spotless with Gradle
- Key Principles for Reducing Continuous Integration Build Time
- Why Distributed CI is the Logical Next Step
.NET
- Continuous Integration with MSBuild and Jenkins – Part 1
- Continuous Integration with MSBuild and Jenkins – Part 2
- MSBuild Tutorial
- Shorter MSBuild Tutorial
- SVN, Hudson and MSBuild – Revision control repository
- SVN, Hudson and MSBuild – Continuous Integration
- SVN, Hudson & MSBuild – Building code on post commit
