In part one we looked at using MSBuild in a general sense. Part 2 we apply that knowledge to a specific continuous integration server, namely Jenkins. We choose Jenkins because it is an open source project that supports a wide variety of projects, making it ideal for heterogeneous environments.
In this first of a two-part series, Mustafa Saeed Haji Ali looks at implementing a continuous integration system using MSBuild. Part two will how to integrate this into Jenkins, an extendable continuous integration server with support for a wide variety of operating systems and programming languages.
Apache Wicket is a powerful, light-weight component-based web application framework with strong separation of presentation and business logic. 1
This article from Atlassian, discusses four aspects of automated builds and continuous integration: communication flow, effective builds, code quality, and automated deployment. 4
Mark Figley talks about enforcing coding standards and best practices in an automated fashion through the build process. 5
Eric Newcomer, co-chair of the OSGi Enterprise work group, talks about the evolution of OSGi and it's relationship to SOA and ESB. 7