-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06)
subversion@2.6
We are using a rather complex SVN structure for our software projects with many externals. Since checkout of externals is rather slow, it happens regularly to us, that a commit is performed to the repository, while the checkout is still running. Unfortunately this causes the externals to be checked out with different (head) revisions - resulting into a "mixed source" warning of our build script later.
Is there any way check out a SVN project with a consistent head revision for all externals?
Is it possible to let the SVN plugin repeat a checkout when a "mixed source" condition is detected?
This problem is a major issue for our Continuous Integration work flow, since it leads to builds with a inconsistent code base (aka mixed revisions).
Therefore it would be nice to implement a workaround for this issue into the SVN plugin.
Here is a possible solution, that is implemented by the TortoiseSVN client (quote from here):
So what should be done for checking out a SVN working copy is: