Hello, i changed the order of cleanUp and revert task in version 1.4.4.40 Cleanup is now called in the first position and should slove your problem.
Please try again. Daniel Raúl Nuño schrieb: > Hi Ruben, > > Yes, I have both revert and cleanUp options set to true. > > Cheers, > > Raúl > > On 28 abr, 08:48, Ruben Willems <ruben.will...@gmail.com> wrote: > >> Hi >> >> you still get this Working copy '.' locked >> when the revert and cleanup are set to true? >> >> with kind regards >> Ruben Willems >> >> On Mon, Apr 27, 2009 at 12:45 PM, Raúl Nuño <rauln...@gmail.com> wrote: >> >> >>> Hi Ruben, >>> >>> I have been testing these new features (revert and cleanUp in the svn >>> source control block) and I get (randomly): >>> >>> <exception><![CDATA >>> [ThoughtWorks.CruiseControl.Core.CruiseControlException: Source >>> control operation failed: svn: Working copy '.' locked >>> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for >>> details) >>> . Process command: C:\Archivos de programa\CollabNet Subversion >>> \svn.exe revert --recursive . >>> at >>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute >>> (ProcessInfo processInfo) >>> at >>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.GetModifications >>> (IIntegrationResult from, IIntegrationResult to) >>> at >>> >>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.MultiSourceControl.GetModifications >>> (IIntegrationResult from, IIntegrationResult to) >>> at >>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications >>> (ISourceControl sourceControl, IIntegrationResult lastBuild, >>> IIntegrationResult thisBuild) >>> at >>> ThoughtWorks.CruiseControl.Core.IntegrationRunner.GetModifications >>> (IIntegrationResult from, IIntegrationResult to) >>> at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate >>> (IntegrationRequest request)]]></exception> >>> >>> Note that the problem is caused by the "svn revert" command. >>> >>> And talking about this, the main problem is still alive, revert and >>> cleanUp options are only trying to fix something not done right. But >>> who is causing these problems? Why is the working copy getting locked? >>> >>> Cheers, >>> >>> Raúl >>> >>> On 21 abr, 21:29, Ruben Willems <ruben.will...@gmail.com> wrote: >>> >>>> Hi >>>> >>>> if your using the 1.4.4 version of CCNet, do not forget to set the >>>> >>> following >>> >>>> options in the svn source control block; >>>> >>> http://confluence.public.thoughtworks.org/display/CCNET/Subversion+So... >>> >>>> revert >>>> and >>>> cleanUp >>>> >>>> with kind regards >>>> Ruben Willems >>>> >>>> On Tue, Apr 21, 2009 at 7:12 PM, Daniël <goo...@twia.nl> wrote: >>>> >>>>> Hi, >>>>> >>>>> We are having similar problems with our CrouseControl servers. >>>>> We are running one server with CCNet 1.4.3, which uses the Collabnet >>>>> client 1.5.0. >>>>> We are running another server with CCNEt 1.4.3.20 using Collabnet >>>>> client 1.6.1. >>>>> Bot have SVN problems with caught signals. I tried to find something >>>>> in the logfiles, but unfortunately the give no clue what the signal >>>>> was. >>>>> I have had several occasions where loggin off my remote desktop >>>>> connection to the Winsows 2003 server running CCNet seems to trigger >>>>> the SVN issue for the project it is currently checking. With the >>>>> checkexternals on, and quite a few externals in our projects and a lot >>>>> of project, our buildserver is virtually always checking or building. >>>>> >>>>> I hope this helps a bit, >>>>> >>>>> Daniël >>>>> >>>>> On 21 apr, 12:31, Raúl Nuño <rauln...@gmail.com> wrote: >>>>> >>>>>> For more information, the error occurred after a successful build (23 >>>>>> minutes). >>>>>> >>>>>> 2009-04-20 17:57:42 (Failed) >>>>>> 2009-04-20 17:34:19 (2) >>>>>> >>>>>> On 21 abr, 11:06, Raúl Nuño <rauln...@gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have been testing the CCNET server and yesterday I had an >>>>>>> >>> exception >>> >>>>>>> when CCNET tried to check for modifications. >>>>>>> >>>>>>> <exception><![CDATA >>>>>>> [ThoughtWorks.CruiseControl.Core.CruiseControlException: Source >>>>>>> control operation failed: svn: Caught signal >>>>>>> . Process command: C:\Archivos de programa\CollabNet Subversion >>>>>>> \svn.exe loghttp://X.X.X.X/svn/Project/Dummy/trunk/source-r >>>>>>> "{2009-04-20T15:34:19Z}:{2009-04-20T15:57:42Z}" --verbose --xml -- >>>>>>> username X --password X --non-interactive --no-auth-cache >>>>>>> en >>>>>>> >>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute >>> >>>>>>> (ProcessInfo processInfo) >>>>>>> en >>>>>>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.GetModifications >>>>>>> (IIntegrationResult from, IIntegrationResult to) >>>>>>> en >>>>>>> >>> ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications >>> >>>>>>> (ISourceControl sourceControl, IIntegrationResult lastBuild, >>>>>>> IIntegrationResult thisBuild) >>>>>>> en >>>>>>> ThoughtWorks.CruiseControl.Core.IntegrationRunner.GetModifications >>>>>>> (IIntegrationResult from, IIntegrationResult to) >>>>>>> en ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate >>>>>>> (IntegrationRequest request)]]></exception> >>>>>>> >>>>>>> Installed in server: >>>>>>> - CruiseControl.Net 1.4.3 >>>>>>> - CollabNet Subversion Client 1.6.0 >>>>>>> - TortoiseSVN 1.6.0 >>>>>>> >>>>>>> I have a lot of problems with the relationship between CCNET and >>>>>>> >>> SVN >>> >>>>>>> ("resource out of date; try updating", "Source control operation >>>>>>> failed: svn: Working copy 'out\main\Release' locked >>>>>>> svn: run 'svn cleanup' to remove locks", some merge errors when >>>>>>> comitting... and more sticky random errors). >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Raúl- Tekst uit oorspronkelijk bericht niet weergeven - >>>>>>> >>>>>> - Tekst uit oorspronkelijk bericht weergeven - >>>>>>
