Hi Randy I'm not sure what you mean by "whether the task running was an actual software build"? Depending on what you are trying to determine, some of the environment variables that CCNet sets might be of use. They are listed on the confluence page for the <exec> task: http://confluence.public.thoughtworks.org/display/CCNET/Executable+Task
For example CCNetBuildCondition could allow you to distinguish between builds that were forced and those that were triggered by someone checking in to the sourcecontrol for the project. Is that the sort of thing you are trying to distinguish? Dave On Wed, Jan 14, 2009 at 5:44 AM, Randy <[email protected]> wrote: > > Can anybody see a downside to adding a field to the .state file? I > was trying to set a boolean environment variable (isBuild = {y,n}) > from within the build based on whether the task running was an actual > software build or not. That didn't work out too well since > environment variables can't be changed from within the environment. > My next thought was to write this status indicator to a file and since > the state file is already being maintaned for each build, it seemed > like a good idea to just add another field. > > However, I don't know what the ramifications would be (would it cause > a problem with some other part of cruisecontrol.net). > > Any thoughts (or any other ideas on how to handle this). > > Also, if the state file is deleted, at what point during the build is > it recreated? > > Thank you, > > Randy Neidigh
