Hi there,
We have a large collection of nAnt scripts that build our various products. They almost all have the following structure:
- Erase old working copy.
- Check out complete fresh copy from version control.
- Increment build number in appropriate file (custom nAnt task).
- Run static analysis (StyleCop, Perl scripts)
- Build solution using Visual Studio - ends up with MSI output.
- Run unit tests (nUnit, JSUnit)
- Run static analysis (FxCop)
- Zip up deliverables (MSI, readme, etc) into well-named package.
- Put this zip package onto a server share.
- Email results to team.
From our research, it seems that CruiseControl(.net?)/Hudson/BuildBot would only add the trigger that causes the build, which at the moment is double-clicking the nAnt script over Remote Desktop and a status dashboard.
Are we missing anything else significant?