-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
Ubuntu 10.10 / Apache / Subversion 1.5.1
- create tag http://svn.test.com/proj_1/tag/test
- create external in http://svn.test.com/proj_2/trunk/dev/ext test that points to http://svn.test.com/proj_1/tag/test
- now rename http://svn.test.com/proj_1/tag/test to http://svn.test.com/proj_1/tag/test_2
If Jenkins is started now, the broken external is not reported and the build will start instead that the build fails with the subversion error.
- duplicates
-
JENKINS-6415 invalid svn:externals warnings are swallowed silently and ignored during checkout
-
- In Progress
-
I had similar issue in my project but the base problem which is described didn't changed. Broken external don't stop build from being executed. If I want to use jenkins with subversion I should be 100% sure that when some problems with svn occurs build will be failed. Now builds runs even if some code wasn't checkout.