[users at bb.net] SourceStamps and TriggerStep

[Jared Grubb]

The Trigger step can specify different properties for different builders, but right now I dont think you can modify the sourcestamp.

Two things you might be able to try:
 - look at steps/trigger.py to see how Trigger does it
 - or pass the sourcestamp changes in a property, and as a first Step in each build, adjust the sourcestamp according to the properties. I think this could work?

Jared

> On Jan 28, 2016, at 11:09, Francesco Di Mizio <francescodimizio at gmail.com> wrote:
> 
> Is it possible at all to dynamically specify a sourcestamp for each scheduler kicked by the a trigger step?
> 
> A bit of brackground: I've inherited a system where each triggered job is using the property named revision in a number of steps. Such a property is passed to the child by its parent through getSchedulersAndProperties. On top of that each child job can be passed a different 'revision'
> 
> What happens is that 'revision'  always ends up being overwritten by the sourcestamp revision of the parent. So all the children eventually get the same revision even though I am setting it myself from within getSchedulersAndProperties.
> 
> I was looking at the code and indeed the sourcestamp gets cooked once and then passed in to each child. What I need is to have the system loop through the children, cook a ss based on the properties and then kick them.
> 
> Pardon the wall of text. Hope this was clear enough at least.
> 
> Francesco
> 
> 
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users