Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17228

Fail build when subversion workspace is locked

      This is a request to backport a Hudson fix into Jenkins. This is a 2-line change done in Hudson Subversion plugin 2.3.3, SHA 37ca9c134702878e6bb824dde108d63c6df043d8

      https://github.com/hudson-plugins/subversion-plugin/commit/37ca9c134702878e6bb824dde108d63c6df043d8

      Rationale: subversion workspace often remains locked if previous svn update failed because of bad network connection, wiping the workspace is not useful for anything in this situation, rather the opposite.

          [JENKINS-17228] Fail build when subversion workspace is locked

          Paavo Helde added a comment -

          We are currently using the "Install Hudson" workaround ...

          Paavo Helde added a comment - We are currently using the "Install Hudson" workaround ...

          Ruben Stein added a comment -

          The link to the fix is broken, if someone could point to these two lines again, one could try to rebuild a patched version.

          Ruben Stein added a comment - The link to the fix is broken, if someone could point to these two lines again, one could try to rebuild a patched version.

          Daniel Beck added a comment -

          if someone could point to these two lines again

          rst It took me a minute to find the new repo location. You can do it if you try!

          Daniel Beck added a comment - if someone could point to these two lines again rst It took me a minute to find the new repo location. You can do it if you try!

          John Dahl added a comment -

          John Dahl added a comment - Please try this link https://github.com/hudson3-plugins/subversion-plugin/commit/37ca9c134702878e6bb824dde108d63c6df043d8

          John Dahl added a comment -

          We are also trying Hudson at the moment, but we are lacking many plugins that are available in Jenkins. Plugins available in Hudson have also stopped updating

          John Dahl added a comment - We are also trying Hudson at the moment, but we are lacking many plugins that are available in Jenkins. Plugins available in Hudson have also stopped updating

          Nick Owens added a comment -

          Please fix this or at least add a toggle to svn settings so you can choose to either "just fail", or "get fresh workspace" if the error is SVNErrorCode.WC_LOCKED

          Nick Owens added a comment - Please fix this or at least add a toggle to svn settings so you can choose to either "just fail", or "get fresh workspace" if the error is SVNErrorCode.WC_LOCKED

          Petr Kubat added a comment -

          Hello, I cant believe nobody touched such an issue for over 4 years. This is really a problem. Is there any official statement from Jenkins maintainers? For example clearly stating that they decided to ignore this issue?

          Petr Kubat added a comment - Hello, I cant believe nobody touched such an issue for over 4 years. This is really a problem. Is there any official statement from Jenkins maintainers? For example clearly stating that they decided to ignore this issue?

          Petr Kubat added a comment -

          Ok, I created a pull request making the same change as was done in Hudson. Let's see what happens.

          Petr Kubat added a comment - Ok, I created a pull request making the same change as was done in Hudson. Let's see what happens.

          Just had this blow up a whole series of builds this morning.  Don't see a good reason why the pull request was rejected.

          Has anyone found a reasonable workaround?  Best I can figure out is to try to checkout in a sub-folder that is safer to have blasted away then go back up to my parent.

          Michael Thompson added a comment - Just had this blow up a whole series of builds this morning.  Don't see a good reason why the pull request was rejected. Has anyone found a reasonable workaround?  Best I can figure out is to try to checkout in a sub-folder that is safer to have blasted away then go back up to my parent.

          Please make it an option to not get a fresh workspace. I have to write custom svn bash and bat files to manually update svn just to prevent this from happening as it takes two hours to checkout our svn and its unacceptable.

          Devon Scott-Tunkin added a comment - Please make it an option to not get a fresh workspace. I have to write custom svn bash and bat files to manually update svn just to prevent this from happening as it takes two hours to checkout our svn and its unacceptable.

            Unassigned Unassigned
            paavo256 Paavo Helde
            Votes:
            20 Vote for this issue
            Watchers:
            21 Start watching this issue

              Created:
              Updated: