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

Subversion update ignores locked workspace on windows

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • subversion-plugin
    • None
    • Jenkins 2.260
      Subversion Plug-in 2.13.1

    Description

      When there is a "broken"/locked working copy, the subversion-plugin should normally delete the working copy and checkout a fresh one (source code).

      But on our windows build agents the locked working copy is simply ignored and build continues.
      There is no error logged indeed, but the checkout stops at this point.
      I noticed the checkout being stopped because our repo consists of several externals and the last entry in checkout log contains the update for the locked external, but the remaining externals are not being updated.
      This causes the working copy not being updated, so we are building an old version without recognizing it.

      In addition this leads the scm trigger being fired again and again, because the old revision of the working copy is saved to the builds/jobs scm information.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-47803 subversion scm is not able to handle locked externals

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            philipph Philipp Homann created issue -
            philipph Philipp Homann made changes -
            Field Original Value New Value
            Description When there is a "broken"/locked working copy, the subversion-plugin should normally delete the working copy and checkout a fresh one ([source code|https://github.com/jenkinsci/subversion-plugin/blob/d18eacb113c33f8822677f411cc4c3c00ad590ff/src/main/java/hudson/scm/subversion/UpdateUpdater.java#L182]).

            But on our windows build agents the locked working copy is simply ignored and build continues.
            There is no error logged indeed, but the checkout stops at this point.
            I noticed the checkout being stopped because our repo consists of several externals and the last entry in checkout log contains the update for the locked external, but the remaining externals are not being updated.
            This causes the working copy not being update, so we are building an old version without recognizing it.

            In addition this leads the scm trigger being fired again and again, because the old revision of the working copy is saved to the builds/jobs scm information.             		When there is a "broken"/locked working copy, the subversion-plugin should normally delete the working copy and checkout a fresh one ([source code|https://github.com/jenkinsci/subversion-plugin/blob/d18eacb113c33f8822677f411cc4c3c00ad590ff/src/main/java/hudson/scm/subversion/UpdateUpdater.java#L182]).

            But on our windows build agents the locked working copy is simply ignored and build continues.
             There is no error logged indeed, but the checkout stops at this point.
             I noticed the checkout being stopped because our repo consists of several externals and the last entry in checkout log contains the update for the locked external, but the remaining externals are not being updated.
             This causes the working copy not being updated, so we are building an old version without recognizing it.

            In addition this leads the scm trigger being fired again and again, because the old revision of the working copy is saved to the builds/jobs scm information.
            ifernandezcalvo Ivan Fernandez Calvo made changes -
            Assignee Ivan Fernandez Calvo [ ifernandezcalvo ]
            philipph Philipp Homann added a comment -

            Noticed that it does not happen on windows only and found that issue (JENKINS-47803).

            philipph Philipp Homann added a comment - Noticed that it does not happen on windows only and found that issue ( JENKINS-47803 ).
            philipph Philipp Homann made changes -
            Link This issue duplicates JENKINS-47803 [ JENKINS-47803 ]
            philipph Philipp Homann made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            allan_burdajewicz Allan BURDAJEWICZ made changes -
            Assignee Allan BURDAJEWICZ [ allan_burdajewicz ]
            allan_burdajewicz Allan BURDAJEWICZ made changes -
            Assignee Allan BURDAJEWICZ [ allan_burdajewicz ] Ivan Fernandez Calvo [ ifernandezcalvo ]

            People

              ifernandezcalvo Ivan Fernandez Calvo
              philipph Philipp Homann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: