-
Improvement
-
Resolution: Fixed
-
Major
Job1 listens for project A
Job2 listens for project B
If project A and B are uploaded with the same topic, and we trigger builds from project A, only Job1 is triggered. If we trigger builds from project B, only Job2 is triggered. In some scenarios what we expect is both Job1 and Job2 are triggered either from project A or B because they are tied by the same topic.
[JENKINS-64783] Gerrit Trigger: Topic Association support
jack mo
created issue -
jack mo
made changes -
| Summary | Original: Gerrit Trigger: missing some builds from event with topic | New: Gerrit Trigger: Better handle of change based event |
jack mo
made changes -
| Description |
Original:
Job1 listens for project A, B
Job2 listens for project A, C If project A, B and C are uploaded with the same topic, and we trigger builds from project B, only Job1 is triggered. If we trigger builds from project C, only Job2 is triggered. What we expect is both Job1 and Job2 are triggered either from project B or C because they are tied by the same topic. In general, jobs should not only triggered by the projects in their configuration, but also by those projects that are dynamically tied to the configured ones by topic. I'm not sure this is a bug or something meant to be. Please correct me if I made any mistakes. |
New:
Job1 listens for project A, B
Job2 listens for project A, C If project A, B and C are uploaded with the same topic, and we trigger builds from project B, only Job1 is triggered. If we trigger builds from project C, only Job2 is triggered. What we expect is both Job1 and Job2 are triggered either from project B or C because they are tied by the same topic. In general, the whole changes of a topic should be taken into account when it comes to determining whether a job should be triggered, not only the change from Gerrit event. I'm not sure this is a bug or something meant to be. Please correct me if I made any mistakes. |
jack mo
made changes -
| Summary | Original: Gerrit Trigger: Better handle of change based event | New: Gerrit Trigger: Topic association support |
jack mo
made changes -
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
jack mo
made changes -
| Summary | Original: Gerrit Trigger: Topic association support | New: Gerrit Trigger: Topic Association support |
jack mo
made changes -
| Description |
Original:
Job1 listens for project A, B
Job2 listens for project A, C If project A, B and C are uploaded with the same topic, and we trigger builds from project B, only Job1 is triggered. If we trigger builds from project C, only Job2 is triggered. What we expect is both Job1 and Job2 are triggered either from project B or C because they are tied by the same topic. In general, the whole changes of a topic should be taken into account when it comes to determining whether a job should be triggered, not only the change from Gerrit event. I'm not sure this is a bug or something meant to be. Please correct me if I made any mistakes. |
New:
Job1 listens for project A
Job2 listens for project B If project A and B are uploaded with the same topic, and we trigger builds from project A, only Job1 is triggered. If we trigger builds from project B, only Job2 is triggered. In some scenarios what we expect is both Job1 and Job2 are triggered either from project A or B because they are tied by the same topic. |
jack mo
made changes -
| Issue Type | Original: New Feature [ 2 ] | New: Improvement [ 4 ] |
jack mo
added a comment - jack mo
added a comment - See https://github.com/jenkinsci/gerrit-trigger-plugin/releases/tag/gerrit-trigger-2.33.0 jack mo
made changes -
| Assignee | Original: rsandell [ rsandell ] | New: jack mo [ jack_mo ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
There is a PR addressing this issue: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/425