The result of Plastic SCM integration with CruiseControl is a complete solution for companies who are using the Continuous Integration pattern for their development as it allows users to automate build and release tasks.

Using Plastic SCM integration with CruiseControl for Continuous Integration, you can continually complete manageable integration issues avoiding large integrations: CruiseControl monitors your Plastic SCM server for any update and triggers a build whenever it detects any new changes to the source code repository. The result is a more reactive agile development environment as developers do not need to wait for scheduled builds, and they will be constantly notified about the project status if any change has occurred.

As CruiseControl integration with Plastic SCM is highly configurable, builds can be scheduled to run at certain times, providing your company flexibility to decide your optimized working method.

Most of developers have had the unfortunate experience of working for several days on a key feature until it works perfectly, only to find out that it no longer works with fresh builds of the other components. If we are lucky, the failure will be obvious such as a compiler error. If we're not so lucky, it will appear to work only to fail later during release testing.

Using CruiseControl with Plastic SCM would solve these painful conflicts as it is like having another member of the team, whose fulltime job is just compiling and checking your code for errors, so any existing error will be immediately found.

You can find information on how to configure Platic SCM with CruiseControl at:

http://cruisecontrol.sourceforge.net/main/configxml.html#plasticscm or in Plastic SCM user´s guide.

If you want to learn more about the continuous integration pattern you can have a look at: Continuous Integration by Martin Fowler and Matthew Foemmel.