Helmut and Ross were working on this same problem: http://groups.google.com.ag/group/ccnet-user/browse_thread/thread/361336474d69706c/9d56964fe5f2feed?lnk=gst&q=Error+Message%3A+ThoughtWorks.CruiseControl.Core.CruiseControlException%3A+Source+control+operation+failed%3A+Given+update+transaction+out+of+range.#9d56964fe5f2feed
But I cant find a resolution. Error Message: 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 7958 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) Project: Opus_Integration Date of build: 2009-02-13 07:30:39 Running time: 00:00:01 Integration Request: Dashboard triggered a build (ForceBuild) Last changed: 2009-02-13 02:22:32 Last log entry: commit latest build revision history I thought that this meant that the workspace was out of sync, but I am now deleting the whole workspace, and doing the update -9 pop...etc...so that can't be it. Now Im thinking that maybe <lastChangeLabeller> in my ccnet.config is grabbing the WRONG transaction number...possibly from another stream? =========================== Error Message: ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: Stream Opus_Integration_unknown already exists . Process command: c:\Program Files\AccuRev\bin\accurev.exe mksnap -s "Opus_Integration_unknown" -b "Opus_Integration_Build" -t "2009/02/13 02:15:00" 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.LabelSourceControl (IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build (IIntegrationResult result) Project: Opus_Integration Date of build: 2009-02-13 02:15:00 Running time: 00:07:32 Integration Request: NightlyDistributionBuildTrigger triggered a build (ForceBuild) I think this one is because I'm using "lastChangeLabeller" and making a snapshot of the build at build time. When I do this, accurev seems to decide sometimes that there are no transactions or differences between most recent build, and last build, or accurev/ccnet just doesn't know what the current transaction number is, so it doesn't have a transaction number to give the label, so it tries to label it "unknown" but can't make a snapshot of unknown, because its already done that. >From what I'm reading online, an upgrade of ccnet to the latest/ greatest MIGHT make this label behave...but Im not sure...I haven't found any proof in the release notes for ccnet that this is corrected. Thanks for any help or responses you may be able to give me. -Russ On Feb 11, 10:27 am, "[email protected]" <[email protected]> wrote: > I just changed the trigger time, and watched the automation run > perfectly. Noerror. > Does anyone have any idea why I get thiserrorso intermittently? > > On Feb 11, 10:19 am, "[email protected]" <[email protected]> > wrote: > > > > > Okay, > > > Im using accurev as mysourcecontrol, and CCNET is triggering a > > scheduled build. Here is myerrormessage: > > > <cruisecontrol project="Opus_Integration"> > > <requestsource="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 > >controloperationfailed:Givenupdatetransactionoutofrange. > > . Process command: c:\Program Files\AccuRev\bin\accurev.exeupdate-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- Hide quoted text - > > - Show quoted text -
