A requirement for keeping the main build green is enabling developers to do something as close to the main build as possible on their local machines. Do you have either:
- a command-line build that developers can run locally that does the same thing as the main build? - a Visual Studio build that is identical to the main build that developers can run before checking in? Dave Cameron CruiseControl.NET - http://ccnet.thoughtworks.com On Sat, Mar 7, 2009 at 3:39 PM, jonty s <[email protected]> wrote: > So my scenario is, I am a start up company with a mix of fresh and > experienced developers. My code is just taking shape and I want to introduce > CC.NET from the start. This will help catch bad checkin's early and my dev's > can gain maturity over time. But during the initial stages my main build > keeps failing. To preempt this, I would like to setup a automated build > process that would > > 1) Lock the Source Repository and any other checkin's > > 2) CO the code, do a buddy build (incremental build only, not fresh) > > 3) Report errors to mailing group X > > 4) Unlock the Source Repository > > 5) Trigger a full build. > > JSiddharth
