[
https://issues.jenkins-ci.org/browse/JENKINS-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160269#comment-160269
]
Roland Schulz commented on JENKINS-11409:
-----------------------------------------
A partial solution would be to combine the messages of several jobs each
triggered by the plugin, before posting them to Gerrit. This would allow one to
tell the plugin to trigger several jobs without getting as many comments (and
emails) in Gerrit.
This would (probably) only help for jobs which are independent (unless it is
somehow possible to wait on the dependent jobs).
> Gerrit-trigger should support waiting for downstream jobs of triggered builds
> -----------------------------------------------------------------------------
>
> Key: JENKINS-11409
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11409
> Project: Jenkins
> Issue Type: Improvement
> Components: gerrit-trigger
> Reporter: Jørgen Tjernø
> Assignee: rsandell
>
> When using gerrit-trigger to trigger a build from Gerrit, gerrit-trigger
> should have support for waiting for downstream jobs to complete (and take
> those into considerations).
> The use case is to have a build job followed by a test job (if the build
> completes), but currently gerrit-trigger will report success as soon as the
> build job finishes.
> The work-around is to create a wrapper job that uses parameterized trigger to
> start a "blocking" build of the build job, followed by a "blocking" build of
> the test job. The downside of this is that the wrapper occupies a slot on an
> executor, even though it just blocks, and that the output in gerrit doesn't
> clearly indicate if building or testing failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
