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

[Matisse Enzer]

Thanks.

alwayUseLatest could work- but I am trying to avoid having two  
builders for each "downstream" repo.
I'll see what's in the works in trac - maybe my team can help move  
things along.

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

(with got you cannot clone an arbitrary subdirectory from a repo as  
you might with e.g. SVN at least I think that's true)

Sent from my iPhone

On Nov 1, 2010, at 2:24 AM, Benoît Allard <benoit at aeteurope.nl> wrote:

>
>
> Matisse Enzer wrote:
>> Is anyone already working on a way to specify the revision to use  
>> in a Trigger step?
>> I want a commit to repository AAA to have a build step that  
>> triggers a build in repository BBB - and so I want to set the  
>> revision to use in repository BBB to 'HEAD'
>
> Hi Matisse, this is not something that works out-of-the-box ...  
> buildbot is currently designed to only track one repository. Multi  
> repositories is work in progress, and can be tracked with the  
> 'buildcoord' keyword in the bug tracker. [1]
>
> For what you are looking for, though, I guess the  
> 'alwaysUseLatest' [2] parameter of any Source Checkout Step could be  
> fitting your needs.
>
> Best Regards,
> Benoit
>
> [1] http://buildbot.net/trac/query?keywords=~buildcoord
> [2] http://buildbot.net/buildbot/docs/current/Source-Checkout.html