![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
23/Jul/12 11:53 AM
|
|
Description:
|
I believe jenkins' build triggering logic was previously changed so as to not trigger downstream builds until all their dependencies have been built, with the side effect that if there is a circular dependency between two or more downstream builds, none of them will be triggered
Unfortunately, there is no indication that this has occurred, and no obvious way to find out why the downstream builds are not running. To the frustrated user it simply appears as though build triggering is not working correctly (with a large number of maven projects, it can be easy to introduce a cyclic dependency without noticing)
Please add some indication or at least logging in the console output as to why a downstream build has not been triggered, so that it's possible to see what has happened and fix the circular dependency.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Michael Donaghy
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
