Jenkins › Jenkins issues

[JIRA] Created: (JENKINS-10260) broken externals are not detected

Classic

List

Threaded

3 messages Options

JIRA noreply@jenkins-ci.org

[JIRA] Created: (JENKINS-10260) broken externals are not detected

broken externals are not detected
---------------------------------

Key: JENKINS-10260
URL: https://issues.jenkins-ci.org/browse/JENKINS-10260
Project: Jenkins
Issue Type: Bug
Components: subversion
Affects Versions: current
Environment: Ubuntu 10.10 / Apache / Subversion 1.5.1
Reporter: Stefan Suffa
Priority: Critical

- 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.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Remove Ads

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-10260) broken externals are not detected

[ https://issues.jenkins-ci.org/browse/JENKINS-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159352#comment-159352 ]

Chris Z commented on JENKINS-10260:
-----------------------------------

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 use jenkins with subversion I should be 100 % sure that when some problem with svn occurs build will be failed. Now build runs even if some code wasn't checkout.

> broken externals are not detected
> ---------------------------------
>
> Key: JENKINS-10260
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10260
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Affects Versions: current
> Environment: Ubuntu 10.10 / Apache / Subversion 1.5.1
> Reporter: Stefan Suffa
> Priority: Critical
>
> - 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-10260) broken externals are not detected

In reply to this post by JIRA noreply@jenkins-ci.org

[ https://issues.jenkins-ci.org/browse/JENKINS-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159352#comment-159352 ]

Chris Z edited comment on JENKINS-10260 at 2/22/12 8:47 AM:
------------------------------------------------------------

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.

was (Author: winotu):
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 use jenkins with subversion I should be 100 % sure that when some problem with svn occurs build will be failed. Now build runs even if some code wasn't checkout.