We had a long-term problem with svn+hudson, namely that if the svn update step fails it sometimes lets the workspace locked, and the next Hudson run noticed this and decided to wipe out the workspace and check out a new one, which takes enormous amount of time and sometimes goes into endless checkout-wipe cycles, depending on the mood of the corporate intranet.
This was recognized as a problem in Hudson and was fixed in Subversion plugin version 2.3.3 (http://wiki.hudson-ci.org/display/HUDSON/Subversion+Plugin). Now we have partially switched over to Jenkins instead of Hudson, but recently we saw the dreaded message again: "Workspace appear to be locked, so getting a fresh workspace" Should we switch back to Hudson, or is it planned to fix this in Jenkins as well? We have Jenkins ver. 1.496, Subversion plugin 1.45. TIA Paavo -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
