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

subversion scm is not able to handle locked externals


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

      Normally, when a locked working copy state is detected (e.g. because the previous build was interrupted during checkout), subversion scm will remove the working copy and does a fresh check out.

      This does not work when the lock is in a working copy (svn:external) sub directory entry. The update of the external will simply be skipped and the working copy will stay in locked state.

      I just realised that I recently commented JENKINS-7009 which might be the same/similar issue.

            Unassigned Unassigned
            gordin Christoph Vogtländer
            1 Vote for this issue
            3 Start watching this issue