Why cant you have different projects with the same working directory? We have several projects that share the same source control working directory and build at different schedules and with different parameters passed to msbuild - so we have continuous integration builds during the day and a release build overnight
The other alternative is to create a custom msbuild or nant project that is built by your one cruise control project. This msbuild/nant project would call devenv with either debug or production parameters based on CCNetBuildCondition to see if the build was triggered by a force build (ie scheduled) or because of changes. If you want to avoid having a release build triggered by somebody doing a force build in the day, you could have 2 interval triggers in your cruise control project - one scheduled for release builds and one for modifications and make sure they have different names. Then in your msbuild/nant script you could check CCNetRequestSource to decide what to build Anthony On Fri, Jul 10, 2009 at 11:23 AM, Craig & Sammi Sutherland<[email protected]> wrote: > > Hi Chris, > > In the current version of CruiseControl.NET (i.e. 1.4.4) this is not > possible. However for the next release (1.5.0) we are adding parameters to > the system which will allow this. > > We've started on the documentation at > http://confluence.public.thoughtworks.org/display/CCNET/Dynamic+Parameters, > but it is still being worked on. Some additional documentation is also > available at > http://csut017.wordpress.com/2009/05/12/dynamic-build-parameters-some-exampl > es/ and > http://csut017.wordpress.com/2009/02/10/triggering-builds-with-parameters/ - > these posts show how to trigger a build with different parameters. > > > Craig > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Chris W > Sent: Friday, 10 July 2009 8:18 p.m. > To: ccnet-user > Subject: [ccnet-user] Conditional Tasks based on Trigger > > > I have a large VB.NET project for which I want continuous debug builds > building throughout the day. I then want a release build building > overnight whilst the debug builds are switched off. I do not want to > use 2 seperate projects since this will force me to use seperate > working directories, and given the size of the code this would be a > problem. Each build (debug or production) is followed by a task to > move the binaries to another directory so they will not overwrite each > others dll's. > > I am using a devenv task to do the builds and was hoping that I could > use a different value for <configuration> depending on which trigger > had kicked off the process. In other words if the debug continuous > trigger kicked the build off then use <configuration>Debug></ > configuration>, but if the scheduled release trigger kicked the build > off use <configuration>Releaseconfiguration> > > How can I do this? > > >
