-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
-
Feature released in Gerrit Trigger Plugin vers. 2.38.0
Situation:
Say I have 3 patches with same topic, patch A, patch B, patch C and their status below,
Patch A: status: merged, branch: develop
Patch B: status: merged, branch: develop
Patch C : status: open, branch: release
On patch C, I reply some key word to trigger only a target job name job_A. However, with the Enable Topic Association enabled, I am end up triggering some other unnecessary jobs besides job_A just because they are labeled with the same topic regardless of different branch. This is definitely NOT an expected behavior.
- duplicates
-
JENKINS-70111 [TopicAssociation] Provide options to prevent triggering jobs when Change status != NEW
-
- Resolved
-
[JENKINS-65462] Gerrit-Trigger-Plugin Bug on 'Enable Topic Association' , which triggers unnecessary jobs by patches which already MERGED.
Summary | Original: Gerrit-Trigger-Plugin Bug on 'Enable Topic Association' , triggers necessary jobs by merged patches | New: Gerrit-Trigger-Plugin Bug on 'Enable Topic Association' , which triggers unnecessary jobs by patches which already MERGED. |
Description |
New:
Situation: Say I have 3 patches with same topic, patch A, patch B, patch C and their status below, Patch A: status: merged, branch: develop Patch B: status: merged, branch: develop Patch C : status: open, branch: release On patch C, I reply some key word to trigger only a target job name job_A. However, with the Enable Topic Association enabled, I am end up triggering some other jobs besides job_A because of the same topic regardless of different branch. This is definetely an unexpected behavior. |
Description |
Original:
Situation: Say I have 3 patches with same topic, patch A, patch B, patch C and their status below, Patch A: status: merged, branch: develop Patch B: status: merged, branch: develop Patch C : status: open, branch: release On patch C, I reply some key word to trigger only a target job name job_A. However, with the Enable Topic Association enabled, I am end up triggering some other jobs besides job_A because of the same topic regardless of different branch. This is definetely an unexpected behavior. |
New:
Situation: Say I have 3 patches with same topic, patch A, patch B, patch C and their status below, Patch A: status: merged, branch: develop Patch B: status: merged, branch: develop Patch C : status: open, branch: release On patch C, I reply some key word to trigger only a target job name job_A. However, with the *Enable Topic Association enabled*, I am end up triggering some other unnecessary jobs besides job_A just because they are labeled with the same topic regardless of different branch. This is definitely NOT an expected behavior. |
Link |
New:
This issue duplicates |
Released As | New: Feature released in Gerrit Trigger Plugin vers. 2.38.0 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |