|
||||||||
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 |
- [JIRA] (JENKINS-15237) Dependent Maven Jobs igno... m.bla...@gmx.de (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... j...@zuchhold.com (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... j...@zuchhold.com (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... m.ro...@itc-ag.com (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... m.ro...@itc-ag.com (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... jcarsi...@java.net (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... jcarsi...@java.net (JIRA)
Given the number of jobs we have, the issue is critical/blocker for us. See http://qa.nuxeo.org/jenkins/job/nuxeo-core-master/
The strange thing is the dependency between projects which is reported when clicking on a fingerprint is right:
But, given the above sample, nuxeo-services-5.6.0 which has no dependency relation with nuxeo-core-master is badly triggered anyway.