Okay,
Im using accurev as my source control, and CCNET is triggering a
scheduled build. Here is my error message:
<cruisecontrol project="Opus_Integration">
<request source="NightlyDistributionBuildTrigger"
buildCondition="ForceBuild">NightlyDistributionBuildTrigger triggered
a build (ForceBuild)</request>
<modifications>
<modification type="promote">
<filename>version_revision_history.txt</filename>
<project>release\Build\</project>
<date>2009-02-10 02:05:17</date>
<user>build</user>
<comment>commit latest build revision history</comment>
<changeNumber>7218</changeNumber>
<version>65/62</version>
</modification>
</modifications>
<build date="2009-02-11 02:00:00" buildtime="00:00:01"
buildcondition="ForceBuild" />
<exception><![CDATA
[ThoughtWorks.CruiseControl.Core.CruiseControlException: Source
control operation failed: Given update transaction out of range.
. Process command: c:\Program Files\AccuRev\bin\accurev.exe update -t
7218
at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute
(ProcessInfo processInfo)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.AccuRev.RunCommand
(String args, IIntegrationResult result)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.AccuRev.GetSource
(IIntegrationResult result)
at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build
(IIntegrationResult result)]]></exception>
</cruisecontrol>
This happens ALOT. I have having the ccnet.config trigger a cmd that
passes some CLI arguments thru accurev to clean my workspace (update
-9 etc..) and this seems to sometimes work...but not always. I think
it might be a matter of timing. I know Im checking in a version file
RIGHT before the build. Could this be the problem? ANY help or advice
or observations would be most appreciated.
thanks in advance,
Russ
