Hi your config looks ok :-( the only thing preventing the cleanup / revert from running is the following : the code checks that the working folder has a subfolder .svn or _svn if not found, do no execute
now comes the trick : which folder is ccnet checking? I'll add more debug.log statements in the code, so in a future version I know what ccnet is doing where if you view the project configuration via the validator / dashboard / project configuration, which folder do you see in the working directory IN the source control block? with kind regards Ruben Willems On Thu, Jun 18, 2009 at 8:58 PM, Yop83 <[email protected]> wrote: > > I uploaded the project config here: > > http://www.mediafire.com/?sharekey=14cae1bed568604b4c17ca8801618ef7e04e75f6e8ebb871 > (The file is called "Aggregates.xml") > > We have multiple project files on our instance of CCNet, so we are > using <cb:include href="myProject.xml"> tags in the main ccnet.config > file. > That is why I did not post it: all of the logic (except a couple of > variables declaration) is done in the project config file. > > I hope this file can answer your questions. > If you need more info, don't hesitate. > > > On Jun 15, 2:31 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > can you post your ccnet.config of the involved project? > > I'm intrested in the following : > > ° do you have a working folder set at the project level ? > > ° your svn section > > > > with kind regards > > Ruben Willems > > > > On Mon, Jun 15, 2009 at 5:54 PM, Yop83 <[email protected]> wrote: > > > > > I'm using CCNet 1.4.4 SP1 (not a clean install, but an update). > > > > > A project got stuck in the "exception" state recently because the > > > working copy was locked. This was a perfect opportunity for me to add > > > the new <cleanUp>true</cleanup> tag in the source control block of > > > that project. > > > > > Of course it wasn't that easy... > > > > > 1. I added the <cleanUp>true</cleanup> under the sourcecontrol block > > > of the affected project. > > > > > 2. I insured the configuration was updated (by going in the "Project > > > Configuration" tag of the web dashboard and seeing that the tag is > > > correctly set to true). > > > > > 3. I forced a build using the web dashboard. > > > > > EXPECTED RESULTS: > > > 4. The build succeeds because of the cleanup command is run against > > > the working directory. > > > > > ACTUAL RESULTS: > > > 4. The build still fails with the "working copy locked" error. No > > > changes. > > > > > SERVER LOG: > > > Here is the server log related to the force build. As you will see, > > > there is no mention of the cleanup command in the SVN arguments: > > > "2009-06-15 11:06:49,658 [Aggregates - Release 1.0:INFO] Building: > > > Dashboard triggered a build (ForceBuild) > > > 2009-06-15 11:06:49,658 [Aggregates - Release 1.0:DEBUG] Starting > > > process [svn] in working directory [D:\Build directory\Aggregates] > > > with arguments [update "D:\Build directory\Aggregates" --non- > > > interactive --no-auth-cache] > > > 2009-06-15 11:06:49,705 [17060:DEBUG] [Aggregates - Release 1.0 svn] > > > svn: Working copy 'D:\Build directory\Aggregates' locked > > > 2009-06-15 11:06:49,720 [17060:DEBUG] [Aggregates - Release 1.0 svn] > > > svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for > > > details) > > > 2009-06-15 11:06:50,033 [Aggregates - Release 1.0:INFO] Integration > > > complete: Exception - 15/06/2009 11:06:49 AM" > > > > > CONFIGURATION OF OUR SERVER: > > > CCNet 1.4.4 SP1 > > > SVN 1.6.2 >
