• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • subversion-plugin
    • None
    • Hudson ver. 1.367, Windows, Matrix Project

      It appeas that hudson left the working copy in a dirty state and can no longer update it correctly:

      Hudson log:
      Hole 'http://xxx' aus Revision -1 in Datei 'xxx'
      At revision 1928
      Hole 'http://yyy' aus Revision -1 in Datei 'yyy'
      Hole 'http://zzz' aus Revision -1 in Datei 'zzz'
      At revision 1928

      tortoiseSVN Log:

      External: yyy
      External failed: yyy
      Error: Working copy
      Error: 'yyy/somedir'
      Error: locked
      Error: Please execute the 'Cleanup' command.

          [JENKINS-7009] working copy partly locked

          Axel Heider added a comment -

          Today, we had this issue with Hudson ver. 1.369 again. Reanson was that the SVN server had a failure during hudson's checkout before. So when Hudson tried again, the build failed silently.

          Axel Heider added a comment - Today, we had this issue with Hudson ver. 1.369 again. Reanson was that the SVN server had a failure during hudson's checkout before. So when Hudson tried again, the build failed silently.

          Axel Heider added a comment - - edited

          Today we had the same issue with 1.380.

          Could the SVN plugin be extended to perform and additional "svn cleanup" when reverting? It do an "svn cleanup" when an error occurs during update/revert?

          Axel Heider added a comment - - edited Today we had the same issue with 1.380. Could the SVN plugin be extended to perform and additional "svn cleanup" when reverting? It do an "svn cleanup" when an error occurs during update/revert?

          Abhi0123 added a comment - - edited

          I am facing the same issue after I restructured the codebase. What did you do to resolve this?

          Abhi0123 added a comment - - edited I am facing the same issue after I restructured the codebase. What did you do to resolve this?

          AxelHeider added a comment -

          Log onto the build machine. Then either run "svn cleanup" followed
          by an "svn update" manually on the affected directories in the hudson
          workspace. Maybe you have to to it explicitly on the directory that
          has the failure. Maybe you even have to delete the directory and
          check it our again - or hudson will do it on th next build.

          On our side the cause of this problem appears to a failing network
          connection to the Apache/SVN Server. Sometimes the socket is closed
          due to an error during hudson's svn updates. An then sometimes the
          directory remeinas locked. However, it only appears with Hudon's
          SVN, I've never hat this problem when using Tortoise or a command
          line client, they properly clean up the locks on errors.

          Please vote for this bug, so it will get fixed.

          AxelHeider added a comment - Log onto the build machine. Then either run "svn cleanup" followed by an "svn update" manually on the affected directories in the hudson workspace. Maybe you have to to it explicitly on the directory that has the failure. Maybe you even have to delete the directory and check it our again - or hudson will do it on th next build. On our side the cause of this problem appears to a failing network connection to the Apache/SVN Server. Sometimes the socket is closed due to an error during hudson's svn updates. An then sometimes the directory remeinas locked. However, it only appears with Hudon's SVN, I've never hat this problem when using Tortoise or a command line client, they properly clean up the locks on errors. Please vote for this bug, so it will get fixed.

          James Dumay added a comment -

          There have been numerous fixes and upgrades to the Subversion plugin in the intervening years between this ticket being filed and today. If this is still a problem, please reopen and comment with reproduction instructions.

          James Dumay added a comment - There have been numerous fixes and upgrades to the Subversion plugin in the intervening years between this ticket being filed and today. If this is still a problem, please reopen and comment with reproduction instructions.

          I'm running into this or a very similar issue with Jenkins 2.60.3 and Subversion Plug-in 2.9 during a pipeline build.

          From what I can see the working copy needs a cleanup after an aborted update (or in my case it was actually a switch from one tag to another).

          The SCM step had been interrupted in the previous build because a parallel build step failed (and using failFast: true).

          During the next build the SCM step simply states:

          ...
          Fetching 'https://server/repo/module1' at -1 into 'C:\path\module5'
          At revision 9864
          
          Fetching 'https://server/repo/module2' at -1 into 'C:\path\module6'
          Fetching 'https://server/repo/module3' at -1 into 'C:\path\module7'
          D         file1.cpp
          Found credentials ...
          AU        file2.cpp
          U         header1.h
          U         header2.h
          ...
          At revision 9864
          
          Fetching ...
          ...

          "module6" is the module where the svn update in the previously build had been interrupted. The unclean state is simply ignored.

          Running svn update manually via TortoiseSVN reveals:

          Updating: C:\path\
          External: Starting externals...  
          External failed:  C:\path\module6
          Error: Previous operation has not finished; run 'cleanup' if it was interrupted  
          Error: Please execute the 'Cleanup' command.
          

           

          Christoph Vogtländer added a comment - I'm running into this or a very similar issue with Jenkins 2.60.3 and Subversion Plug-in 2.9 during a pipeline build. From what I can see the working copy needs a cleanup after an aborted update (or in my case it was actually a switch from one tag to another). The SCM step had been interrupted in the previous build because a parallel build step failed (and using failFast: true). During the next build the SCM step simply states: ... Fetching 'https: //server/repo/module1' at -1 into 'C:\path\module5' At revision 9864 Fetching 'https: //server/repo/module2' at -1 into 'C:\path\module6' Fetching 'https: //server/repo/module3' at -1 into 'C:\path\module7' D         file1.cpp Found credentials ... AU        file2.cpp U         header1.h U         header2.h ... At revision 9864 Fetching ... ... "module6" is the module where the svn update in the previously build had been interrupted. The unclean state is simply ignored. Running svn update manually via TortoiseSVN reveals: Updating: C:\path\ External: Starting externals...   External failed:  C:\path\module6 Error: Previous operation has not finished; run 'cleanup' if it was interrupted   Error: Please execute the 'Cleanup' command.  

          I have just setup 2.126 with latest subversion plugin.

          I continue to face this issue. Intermittent network connection throws the following error:

          "Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: Connection reset"

          and then 

          "Workspace appear to be locked, so getting a fresh workspace Cleaning local Directory ."

           

          Please let me know what can be the possible remedy. We are currently stuck with out build.

           

          Purushendra Singh added a comment - I have just setup 2.126 with latest subversion plugin. I continue to face this issue. Intermittent network connection throws the following error: "Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: Connection reset" and then  "Workspace appear to be locked, so getting a fresh workspace Cleaning local Directory ."   Please let me know what can be the possible remedy. We are currently stuck with out build.  

            Unassigned Unassigned
            axelheider Axel Heider
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: