How to Do the SVN Cleanup Before Updating the files
swathikumar yenugula
Currently i am using Jenkins with SVN.
Some times while updating the SVN files it is throwing the error
Directory has been locked. Please do the SVN cleanup.
For avoiding this error i have to do the SVN cleanup before updating
the SVN files.
Is there any Plugin available for doing this.
or
Please let me know , how to execute the script file before updating
the files.
Thanks
SwathiKumar
grayaii
there is indeed another process locking a file in our workspace.
In our Jenkins job configuration we have some jobs "Always check out a fresh
copy" while others we have "use SVN Update as much as possible".
Usually this happens when a rogue process is locking a file, and so far
we've only seen this happen on our Windows slave machines. I use Process
Explorer to figure out what process is locking the file and then I kill it.
With Process Explorer, simply press Ctrl+F and search for name of your
workspace directory name, and you'll find the process that has a handle to
it.
Of course, don't simply kill the process. Find the root cause on how you
got into that state and find a solution so that it doesn't happen again.
Good luck!
--
View this message in context: http://jenkins.361315.n4.nabble.com/How-to-Do-the-SVN-Cleanup-Before-Updating-the-files-tp4095563p4096168.html
Sent from the Jenkins users mailing list archive at Nabble.com.
Didier Durand
You can use the option "Always start with a fresh copy" in Project
configuration > Source Code management > Checkout strategy
regards
didier
On Nov 22, 4:42 pm, grayaii <george.g...@rsa.com> wrote:
> We use SVN for all of our 500+ jobs and the only time we get this error if
> there is indeed another process locking a file in our workspace.
>
> In our Jenkins job configuration we have some jobs "Always check out a fresh
> copy" while others we have "use SVN Update as much as possible".
>
> Usually this happens when a rogue process is locking a file, and so far
> we've only seen this happen on our Windows slave machines. I use Process
> Explorer to figure out what process is locking the file and then I kill it.
> With Process Explorer, simply press Ctrl+F and search for name of your
> workspace directory name, and you'll find the process that has a handle to
> it.
>
> Of course, don't simply kill the process. Find the root cause on how you
> got into that state and find a solution so that it doesn't happen again.
>
> Good luck!
>
> --
> View this message in context:http://jenkins.361315.n4.nabble.com/How-to-Do-the-SVN-Cleanup-Before-...
