Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: subversion-plugin
-
Labels:None
-
Environment:sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1
-
Similar Issues:
Description
Using the "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'" svn strategy, we recently had a branch merged into
trunk that added some files. When the Jenkins jobs configured as above
ran against trunk, those added files had their content duplicated.
A quick google suggested it has happened before:
Attachments
Issue Links
- is duplicated by
-
JENKINS-18140 SVNKit 1.7.6 library used in Jenkins causes file contents SVN checkouts to become duplicated
-
- Resolved
-
Hey LuFrija,
If my memory is correct, I had to do the same thing - modify the build command for SVNKit, then copy the resultant jar file into my local maven repo, then build subversion-plugin against that.
This seems like a hacky workflow, but it's the best I could stitch together given there are no instructions on how to build this properly, and the mailing list didn't respond to my question on how to build the correct way.
Are you good to go now?
-Kenny