Fog Creek Software
Discussion Board

Build and release management tools for .NET?

I'm looking for a package that will:

1. Perform builds of my .NET project from SourceSafe. Normal stuff; build it, log any errors, email someone, etc. Basically NAnt or BuildIT type stuff. )

2. Run my NUnit test cases against my code and log the results.

3. Integrate with a bug/feature tracking system so that each build can automatically generate release notes of what bugs, fixes, features have been added since the last release build. I'd want to edit the notes, but doing this gives me a starting point.

4. Make me a cup of coffee each morning.

Basically, I want to be able to run the system, get a release build, get a log to ensure that my unit tests passed and have the release notes at least started for me.

The integration with a bug tracking system is really what is key for me. I'd want to be able to ask the system "what release did we fix this issue and when did we release it?"

I know that's a tall order, but is there anything that comes close?

Mark Hoffman
Thursday, June 19, 2003

You could start with either of these build tools:
Visual Build:
or FinalBuilder:

and add your own custom actions (for example for unit tests), or even write your own control batch or script file which calls one of these build tools as one of the steps in the batch/script and also calls your unit tests and sends a signal to your coffee-maker.

Philip Dickerson
Thursday, June 19, 2003

You can use RFC 2324 ( to make your coffee for you.

Thursday, June 19, 2003

Offshore Indian operator?
What about
>4. Make me a cup of coffee each morning.
you ask?

Your specification did not request you had to be able to drink it too, now did it?

Just me (Sir to you)
Friday, June 20, 2003

On a more serious note. Take a look at
It maybe does not do everything you want yet but Jan Tielens, the developer, is very open to suggestions for extentions.

"Hippo.NET is a tool for streamlining the build process of .NET projects in a team envirionment. It provides continuous integration by monitoring the shared Visual SourceSafe database and starting the build process when changes are detected. An important design goal is to provide a nice and easy-to-use user interface, to monitor builds and trigger the build process when needed. "

"Current features
Client/server model
Trigger build from remote clients
Implements the build process proposed by Microsoft
Automatic build number updates in AssemblyInfo files
Build history information
Current activity information
Fully configurable
Rich Windows Forms UI
Multiple projects
Event notification, eg. MSN Messenger style

Future features
Scheduled builds
Automatic builds after changes"

Just me (Sir to you)
Friday, June 20, 2003

There is a .NET version of CruiseControl:

Oren Miller
Friday, June 20, 2003

Thanks for the replies everyone!

Mark Hoffman
Friday, June 20, 2003

4) Morning Coffee

Friday, June 20, 2003

Sorry, that was a bit long:

The last part should read


(nothing after the last equals).

Friday, June 20, 2003

Yep as one poster mentioned Cruise Control (if there is a .NET version).

I'll point out that Cruise Control + CVS + ANT have been doing this for YEARS now in Java environments.

This is part of Martin Fowler's concept called "Continuous Integration".

James Nicoll
Friday, June 20, 2003

I keep hearing Martin Fowler mentioned... But I think it's funny. I guess you have to be from the UK...

(free lollipop to the first person who works out what i am on about)

Friday, June 20, 2003

*  Recent Topics

*  Fog Creek Home