Chapter 7. Advanced CI tools and recipes

 

This chapter covers

  • Tools and recipes for continuous integration
  • Approaches for integrating different artifact types
  • Strategies and tooling for staging artifacts

This chapter provides techniques to help you implement advanced continuous integration (CI). As you learned in earlier chapters, CI is the backbone of an Agile ALM. But why do we need to discuss advanced CI? CI is a widespread discipline. Its basic concepts are widely understood and supported by all build servers (such as Jenkins, Bamboo, TeamCity, Continuum, and CruiseControl), but advanced topics, such as those I cover in this chapter, are rarely covered elsewhere. This chapter explains how to implement Agile ALM in the context of CI, as illustrated in figure 7.1.

Figure 7.1. Advanced CI scenarios for Agile ALM that are covered in this chapter: building and integrating platforms or languages (.NET and integrating Cobol by using Java and Ant), enabling traceable deployment of artifacts, building artifacts for multiple target environments (staging these artifacts by configuration, without rebuilding them), bridging different VCSs, and performing audits.
Note

If you’re interested in CI basics that we don’t cover in this book, consider reading Continuous Integration: Improving Software Quality and Reducing Risk by Paul. M. Duvall (Addison-Wesley, 2007) or Martin Fowler’s free online resources (http://martinfowler.com/articles/continuousIntegration.html).

7.1. Integrating other artifact types: Cobol

7.2. Integrating other artifact types: .NET

7.3. Configure: building (web) apps for multiple environments

7.4. Building, auditing, and staging with Jenkins

7.5. Using Git and git-svn bridge for feature branch–driven CI

7.6. Summary

sitemap