[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven

Tue, 20 Nov 2012 06:36:53 -0800

Successfully tested on 1.491 with a cherry-pick of 4043905580df5bf22cde0eaf3dec103abdc88017

I tried with https://github.com/nuxeo/nuxeo-common/ and https://github.com/nuxeo/nuxeo-runtime/ with their "master" and "5.6.0" branches.
I couldn't try much more with https://github.com/vietj/chromattic and https://github.com/vietj/wikbook because of build issues but it seems fine on the POM parsing part.

Before the fix, nuxeo-common master (version 5.7-SNAPSHOT) was triggering nuxeo-runtime master (version 5.7-SNAPSHOT) and 5.6.0 (version 5.6.0-HF04-SNAPSHOT), whereas nuxeo-common 5.6.0 was triggering nothing at all.
Note I didn't try to reproduce the issue with chromattic and wikbook before the fix.

However, even if the triggering is fixed, I still have an issue (I don't know if it's exactly the same issue):

  • relationship between builds is sticked at builds earlier the fix
  • if there was no build before the fix, then the relationship is empty

I'm talking about jenkins/projectRelationship?lhs=nuxeo-common-5.6.0&rhs=nuxeo-runtime-5.6.0 and jenkins/projectRelationship?lhs=nuxeo-common-master&rhs=nuxeo-runtime-master
Before 1.480, the relationship is right.
Since 1.481 until 1.491, without the current fix, the relationship seems still right even if triggering is wrong (see comment-168178 on JENKINS-15237).
With the current fix applied on 1.491, the relationship is no more updated (new builds are ignored).
Of course, that new issue appears on the summary views: upstream/downstream information on jobs is right whereas upstream/downstream information on builds is simply missing.
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

Reply via email to