[Buildbot-devel] Passing properties to dependent builders

[Elliot Saba]

I was actually using a Dependent scheduler, but yes using a triggerable
scheduler would have worked as well it seems. Thanks!
On Sep 11, 2014 11:27 PM, "Vasily" <vasslitvinov at pisem.net> wrote:

> Hi Elliot,
>
> I guess you're using Trigger to start dependant builders. If that is true,
> have a look at its documentation, especially the parameter named
> "set_properties", which does exactly what you need - allows you to pass
> some properties from triggering build to the tgriggered one.
>
> Thanks,
> Vasily
> 12 сент. 2014 г. 8:16 пользователь "Mikhail Sobolev" <mss at mawhrin.net>
> написал:
>
>> Hi Elliot,
>>
>> On Thu, Sep 11, 2014 at 05:34:41PM -0700, Elliot Saba wrote:
>> > Hello there, I have a buildbot setup for testing followed by uploading,
>> and
>> > I'd like the upload builders to have access to the properties setup by
>> the
>> > testing builders.
>> When I read the first part of this sentence I thought ("one builder,
>> several steps, build, then upload"), when I read the second part I got
>> completely lost :)
>>
>> > As far as I can tell, properties are not automatically
>> > passed probably because the dependency relationship is between
>> > schedulers not builders, and I can therefore have an upstream
>> > scheduler run multiple builders, each of which sets different values
>> > for a certain property.  Which property a dependent scheduler passes
>> > down to its builders would then be ill-defined.
>>
>> While this part gives a bit of insight into your configration, a bit
>> more information how your build and testing builders are related would
>> really be appreciated.  If for some reasons you can't share your set,
>> maybe you could write a pseudo-setup that has essential links in it?
>>
>> > Is there some method for communicating values from one to the other
>> > though?  This would be really useful, right now I'm writing out files
>> > to `/tmp` which seems like a pretty ugly hack.
>> This would only use if your builders are all running on the same
>> machine.  Otherwise, be prepared for surprises.
>>
>> --
>> Misha
>>
>>
>> ------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce
>> Perforce version control. Predictably reliable.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20140912/90ab8eae/attachment.html>