• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None

      We sometimes face an issue in Jenkins that when an svn update step fails it locks the workspace, so when the next build is run it notices this and decides to wipe out the workspace and check out a new one, which takes enormous amount of time to build it again.

      --------------------------------------------------------------------------------------------------------------
      [02:38:31] - Update dev
      Success build fororg.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder@1cae7e0
      Updating http://repos/wss/soseco/dev at revision '2017-03-08T18:35:59.190 +0530'
      At revision 311237

      Updating http://repos/wss/soseco/dev at revision '2017-03-08T18:35:59.190 +0530'
      Workspace appear to be locked, so getting a fresh workspace
      Cleaning local Directory ../../../src/dev
      Checking out http://repos/wss/soseco/dev at revision '2017-03-08T18:35:59.190 +0530'
      --------------------------------------------------------------------------------------------------------------

      Instead of getting a fresh workspace, it should simply fail the build. And then the user can check why it happened and do svn cleanup.

          [JENKINS-42798] SVN update failure causes fresh checkout

            Unassigned Unassigned
            beastmode Beast Mode
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: