Hi
in the current version of ccnet it is possible, if you use a build script. Give each trigger a unique name (the name property) in the build script, you can check on this name, and do the debug / release compile integration property name : CCNetRequestSource with kind regards Ruben Willems On Fri, Jul 10, 2009 at 10:18 AM, Chris W <[email protected]>wrote: > > 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? >
