|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I can't tell what action has been taken on this defect recently. I installed http://repo.jenkins-ci.org/releases/com/sonyericsson/hudson/plugins/gerrit/gerrit-trigger/2.13.0-beta-2/gerrit-trigger-2.13.0-beta-2.hpi on my Jenkins server and, although it did seem to fix the "missing builds" issue, now I'm only getting one of multiple jobs reporting results back to Gerrit! When I submit a patch set to our Gerrit server, I only get one email but that email shows just one job that was triggered but indicates that the job triggered is 1 of 2. When I go to the review in Gerrit, it only shows one of the two jobs being triggered. This is what I see in Gerrit:
jenkins
12:32 PM
↩
Patch Set 1:
Build Started http://jenkins-instance:8080/job/test-2/37/ (2/2)
I should be seeing:
jenkins
12:32 PM
↩
Patch Set 1:
Build Started http://jenkins-instance:8080/job/test-1/37/ (1/2)
Build Started http://jenkins-instance:8080/job/test-2/37/ (2/2)
I see this with 2.13 beta 2 through 5. I tried 2.13 beta 6 and it fixed this but then I ran into the missing builds defect again.
Has anyone else seen this? I could use some suggestions. This is preventing us from putting our upgraded Jenkins instances into our production environment.