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

[Vitali Lovich]

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 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?

Thanks,
Vitali
 
> On May 21, 2015, at 2:51 AM, Mikhail Sobolev <mss at mawhrin.net> wrote:
> 
> Hi Vitali,
> 
> On Wed, May 20, 2015 at 05:13:07PM -0700, Vitali Lovich wrote:
>> I’m seeing weird behavior where it looks like the properties propagated into
>> a TriggerableScheduler by the Trigger step are missing when I hit rebuild.
>> 
>> Is this intentional behavior?  Is there a way to get the value to persist?
> Could you please describe your scenario and tell the version of Buildbot you
> are observing this behaviuor?
> 
> In our configuration we have a TriggerableScheduler and a Trigger step that
> passes a property with the name of file to test and if I hit 'Rebuild' button
> on the build page, the new build retains this property.  Buildbot 0.8.12.
> 
> -- 
> 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