[Buildbot-devel] Setting the revision to use in a buildbot.steps.trigger.Trigger (for cross-repository triggering)

[Benoît Allard]

Hi Matisse,

Matisse Enzer wrote:
> Thanks.
> 
> alwayUseLatest could work- but I am trying to avoid having two builders 
> for each "downstream" repo.

I don't see how this would imply two builders, just two Source steps, 
and both can (and have to) happen on the same builder if you want anyway 
the source of both repository on the same place. A source step is just 
one more step inside your builder config.
The drawback of this method is that it won't be possible to ask buildbot 
to make a specific build again, as for each build, he now will store 
"useLatest" instead of the right revision.

> I'll see what's in the works in trac - maybe my team can help move 
> things along.

That would be really great ! For now, buildbot has an internal state 
called "SourceStamp". The goal is to introduce an "AggregateSourceStamp" 
that would, well, be the aggregation of multiple SourceStamps, such 
that, and here comes the part that interest you, this object could be 
given to the Source Step and care about *all* the repositories.

> 
> Because of the tendency with git to use several smaller repos I suspect 
> this issue comes up more as gut becomes more widespread.

You are completely right, that is something highly demanded, to an 
extend that some people built their own tool to replace the SCM tool, 
(git in your case) such that with one command, multiple repositories are 
fetched, diffed, and so on ... Such a tool that emulate "git" is called 
"repo" [1].

[1] http://source.android.com/source/git-repo.html

Best Regards
Benoît

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6031 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://buildbot.net/pipermail/devel/attachments/20101102/e3c9e86e/attachment.bin>