Hi
the state file is recreated at every build, so to just store an extra value there, is not recommended, unless you adjust the source. with kind regards Ruben Willems On Tue, Jan 13, 2009 at 7:44 PM, 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
