jenkinsci / jenkinsci/subversion-plugin
[JENKINS-47803] subversion scm is not able to handle locked externals
- Dominant language
- Java
- Stars
- 131
- Forks
- 275
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 6
Description
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">JENKINS-7009 which might be the same/similar issue.
---
Originally reported by 
gordin, imported from: subversion scm is not able to handle locked externals
Raw content of original issue
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.
Contributor guide
Assessment
This issue has not been assessed yet.