Re: The NUnit reference goes away with Clean builds

Charlie Poole <[email protected]> wrote:

> I've used a compromise, where the devtools are checked out
> or updated by the developers only on an as-needed basis.
> The build server checks them out with every build, generally
> in a stub script that also checks out the "real" build script.

Unfortunately, we have 5 different CI build servers, with about 100
different projects spread over them.  An additional "release" build
server, which builds and packages up to a couple of dozen applications
for each of our (internal) product releases, is building 5 to 10
releases at any given time, building each one at least once per day.
Keeping the builds fast was not compatible with checking out, or even
exporting, the tools with every project build. :)

We probably could have overcome the problem, but it seemed easier at the
time to just not do it.

I still keep the tools in Subversion, but in their own repo, with a
working copy on each build server, so that I can easily update each of
the build servers, and set up a new one in a relative flash if I so
need.  It also allows the individual developers to update only as
needed.  We do occasionally have a problem with a project using a newer
version of a tool, such as NUnit, than a developer has installed.  With
our setup, though, it's relatively painless for them to upgrade,
especially with NUnit.

Brad 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace