We have our source code stored in Kiln/Mercurial repositories; we use MSBuild to build our product and we have Unit Tests that utilize MSTest (Visual Studio Unit Tests).

What solutions exist to implement a continuous integration machine (i.e. Build machine).

The requirements for this are:

• A build should be kicked of when necessary (i.e. code has changed in the Repositories we care about)
• Before the actual build, the latest version of the source code must be acquired from the repository we are building from
• The build must build the entire product
• The build must build all Unit Tests
• The build must execute all unit tests
• A summary of success/failure must be sent out after the build has finished; this must include information about the build itself but also about which Unit Tests failed and which ones succeeded.
• The summary must contain which changesets were in this build that were not yet in the previous successful (!) build
• The system must be configurable so that it can build from multiple branches(/Repositories).

Ideally, this system would run on a single box (our product isn't that big) without any server components.

What solutions are currently available? What are their pros/cons? From the list above, what can be done and what cannot be done?

Thanks