Details
-
Improvement
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
-
Blue Ocean - Candidates
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Sprint | GSoC - Coding Phase 2 [ 581 ] |
| Rank | Ranked higher |
| Sprint | GSoC - Coding Phase 2 [ 581 ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Sprint | GSoC - Coding Phase 3 [ 591 ] |
| Rank | Ranked higher |
| Epic Link |
|
JENKINS-53714 [ 194213 ] |
| Rank | Ranked higher |
| Sprint | GSoC - Coding Phase 3 [ 591 ] |
| Sprint | Blue Ocean - Candidates [ 441 ] |
| Rank | Ranked higher |
if someone approves, and the build has started to merge, how do we handle a race condition when a next person approves?
as in, the webhook would be triggered a second time, and the job would make a second attempt at merging (and likely fail, or maybe just have no impact on the merge but use up the jenkins resources for no reason)