[
https://issues.jenkins-ci.org/browse/JENKINS-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163413#comment-163413
]
Armando M commented on JENKINS-11409:
-------------------------------------
I think you should be able to use a trigger from the build step, rather than
the trigger from the post-build section. This is because the former will let
the upstream job wait/block on the downstream project to finish. I had the same
problem and I solved like this. The trigger also posts the results from the
downstream project, so as far as I can tell, this is not a gerrit-trigger issue.
> 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
