<html><head></head><body>I use a local worker which its only job is to coordinate the triggers and the triggered builds and wait for all of that to finish.<br>
Nothing is actually built on the local builders, so, having them wait is not an issue and it never occupies an actual worker.<br>
<br>
Makes any sense for your use case?<br>
<br>
Best,<br>
Pedro.<br><br><div class="gmail_quote">On February 14, 2018 12:45:43 AM GMT+00:00, Will Rosecrans <wrosecrans@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">I have a buildbot job that builds some software, makes a binary, and then triggers a separate job to run some tests that only need the binary while it continues running some tests that require the full source. I am impatient, so I want the triggered job to run asynchronously from the rest of the build. (Both take ages). But I would still like the overall job to fail if the triggered builder fails.<br><br>So is there some way for me to set a property in the builder saying something like the job ID # of the triggered build, that I could use in a step at the end of the triggering build to poll for completion status of the triggered build?<div><br></div><div>Having to refactor things so that the controlling build's tests could run as another triggered build would mean having to upload the whole massive half-built source tree to the master, and then schlep it to another worker machine to run those tests -- and it would leave the machine that currently runs the tests just sitting idle occupying a build machine waiting for the triggered jobs to finish. So I'd like to avoid going that route in this particular scenario, even if the master-controller that just triggers is usually recommended for this sort of thing generally. (I already have a master controller that triggers builds on all the OS's)</div><div><br></div><div>Any clever ideas?</div></div>
</blockquote></div><br>
Pedro Algarvio @ Phone</body></html>