[users at bb.net] Buildbot Triggerable Scheduler and working dir relation

[Francesco Di Mizio]

Ciao Sergio,

Not sure I get your point but cant you simply pass in cwd as a property and
then use it as cwd for whatever you need to do?
More in general though, if you kick a triggerable scheduler you should know
where things end up, like grabbing the previously compiled binaries and
placing them somewhere in a folder (your ccwd perhaps?). I am wondering if
you actually need an other builder to package what you've just
compiled/built (unless of course you need a number of different packaging
means like profile/release).


On Fri, Jan 27, 2017 at 7:27 PM, Andrej Rode <andrej.rode at ettus.com> wrote:

> Hi Sergio,
>
> >
> > My understanding was that a Triggered builder would be run in the same
> > working dir of the "calling" builder but I think I'm not understanding
> > how to correctly configure the builders/schedulers correcty.
>
> If you trigger a TriggerableScheduler this schedulers kicks off new and
> independent builds (you can propagate properties in the Trigger step)
> which are assigned to available workers.
> In fact the build can be delegated to the same worker or another worker
> depending on availability. So you should structure your build "chain"
> independently and use properties to transfer information between
> triggered builds.
>
> Maybe you can make use of transfer steps to move your build directory to
> the master and then download it on the package builders or even start a
> new build on the package builders depending if you want to change build
> arguments (Debug->Release).
>
> Cheers,
> Andrej
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170128/eadd5a7d/attachment.html>