[Buildbot-devel] Is it possible to update the sourcestamp?

[Vitali Lovich]

Are you setting updateSourceStamp=True in your Trigger?

Instead of manually propagating the revision, would using alwaysUseLatest in your SCM/trigger step work?
There’s also a sourceStamps attribute in the Trigger step for setting custom source stamps I think.


-Vitali

> On Jun 10, 2015, at 4:37 PM, Francesco Di Mizio <francescodimizio at gmail.com> wrote:
> 
> The source stamp is being set by a force scheduler (S) which is exposing branch and revision.
> The builder (let's call this K as Kicker) associated with  S kicks off an other scheduler with a trigger step (say T). 
> 
> When I type in a number for the revision in S, the revision gets propagated ok all the way down to the triggered scheduler.
> 
> When I leave it blank, the revision is empty therefore it'll be empty for any kicked off build. I can not pass through got_revision because builder K does not even have a source step, therefore got_revision never gets set.
> 
> So my idea was: well I can just add an other step at the very top of builder K that figures out latest revision and then passes it along to any kicked build. That works in the sense that in the K's UI i can see it being set but does not get propagated even though I am telling it to in the trigger step T. 
> 
> I guess the reason is that what I am doing does not actually change the sourcestamp, just a property whose name happens to go by the same name.
> 
> Is it possible to extend say ShellCommand and retrieve and change the SStamp in there? 
> Any suggestions?
> 
> Cheers!
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel