Chapter 1. Understanding continuous integration
Figure 1.1. In the CI process, developers check code into the version control repository. The automated CI system polls the repository for changes and then builds and tests the code. Results are posted to a feedback system where team members can see the results.
Figure 1.2. The miniCI application builds updated files, tests and deploys them, and then keeps checking for changes in the source code files.
Figure 1.3. TortoiseSVN integrates into Windows Explorer to make it easy to manage your Subversion repository.
Figure 1.4. Part of the XML configuration file for CruiseControl.NET
Figure 1.5. MSBuild Sidekick from Attrice makes it easy to develop and maintain MSBuild scripts.
Figure 1.6. NUnit runs unit tests on your code and reports the results as red/green for failure or success.
Figure 1.7. FxCop reports problems in code that can be issues with design, performance, security, or localization.
Figure 1.8. The StyleCop GUI integrates with Visual Studio and reports issues with coding style.
Figure 1.9. NCover reports the results of testing code paths through the application.
Figure 1.10. You’ll create a CI process for an application consisting of one shared library with two UIs: Windows and web.
Figure 1.11. Different project directory organization structures. Files can be grouped in logical collections. Pick a pattern that suits you.