|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
OK, I have just submitted a pull request adding this feature. I hope it makes it into the plugin soon. It works by adding a "delayed approval" setting to the Gerrit Trigger. When this is selected, the triggered job no longer auto-submits its result. Instead, there is a post-build action available which the downstream job will have to run. It needs to have a job name and a build number as a parameter, so these will need to be passed on as build variables.![]()
If there is enough interest, it can always be improved on later ![]()
So as to solve the above problem of waiting forever, the "flexible publish" plugin can be used. Set it so you only do the delayed approval on your upstream project if it fails (thus not triggering downstream). In the most downstream project you can set it to always do the delayed approval.
As you see this is still pretty manual, but it is a first draft, and has the benefit of working