| Issue 3295: | gerrit-trigger with dependency needs option to abort/un-queue itself if the upstream job fails | |
| 1 person starred this issue and may be notified of changes. | Back to list |
***************************************************************** ***** ***** ***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!! ***** ***** ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD, ***** ***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.***** ***** ***** ***** THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS ***** ***** ***** ***************************************************************** Affected Version: What steps will reproduce the problem? 1. Create a gerrit repository and two jenkins projects (e.g., 'build_x' and 'snapshot_x') that both use the gerrit-trigger plugin to trigger builds upon changes to that repo. 2. In the snapshot_x project, under Gerrit Trigger, click 'Advanced' and next to 'Other jobs on which this job depends' add 'build_x' 3. Submit a review that immediately exits with failure What is the expected output? What do you see instead? Expect: Upon submitting the failing review, build_x will queue. When it fails, nothing more will happen. What I see is: build_x and snapshot_x are both queued. build_x fails, then snapshot_x runs and fails. Please provide any additional information below. Note, I know there are other ways to do this and I've tried most of them, but this option was the closest to what we wanted because I can have the 'silent' flag and I can add a dynamic trigger configuration (e.g., topic=snapshot)
Apr 14, 2015
Project Member
#1
huga...@gmail.com
Status:
Invalid
|
|
| ► Sign in to add a comment |