Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day.
Continuous Integration is a wonderful and popular practice in the software development universe. Yet, for whatever reason, it seems much less commonly utilized in the SharePoint community. SharePoint (naturally) throws a few wrinkles into the process, but no substantial roadblocks, and the benefits of CI can be realized just as well on SharePoint projects as anywhere else. In this session, you'll learn why you should implement a CI process and then see how to do it using TFS and Visual Studio.
Continuous Integration (CI) is probably best suited to projects with the following characteristics:
- Development-oriented – perhaps with more than, say, 3 Visual Studio projects
- Multiple developers
- Fairly long-running (e.g. > 2-3 months; to give the team a chance to implement CI alongside the actual deliverables)