[Buildbot-devel] Trigger properties are treated as runtime properties?

[Vitali Lovich]

> On May 25, 2015, at 10:46 AM, Mikhail Sobolev <mss at mawhrin.net> wrote:
> 
> Hi Vitali,
> 
> On Thu, May 21, 2015 at 10:55:21AM -0700, Vitali Lovich wrote:
>> It’s on 0.8.10.  I have a property I set as a runtime property in a builder.
>> The builder then triggers a TriggerableScheduler passing on this property via
>> set_properties.
> I wonder how exactly do you set a property?  I'd like to reproduce the
> behaviour, so I'd need as many details as possible.
via set_properties.  The source property is a runtime property.
Do you know if the set_properties propagation into the triggered build somehow propagates this?
Where in the code is the value persisted?  Maybe I can instrument it?

>> I can’t tell if it’s all the time, but it seems like it at least happens
>> regularly.  The reason I notice is that I’ve started sending myself an e-mail
>> when it’s missing, but I don’t know when users hit rebuild so I can’t
>> correlate the two.
>> 
>> Is it a problem where properties that are runtime properties for the current
>> builder but don’t get persisted when they’re passed on due to triggering?
> I only could answer this if I could reproduce the situation.
I’m not even sure if it’s deterministic unfortunately.

> -- 
> Misha
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud 
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel