[Buildbot-devel] override revision being checked out

[Vitali Lovich]

I’m checking out the same repository multiple times within the same build, so I’m not quite sure I see how multiple codebases are relevant here.

-Vitali

> On Nov 24, 2014, at 10:30 AM, Jared Grubb <jared.grubb at gmail.com> wrote:
> 
> If you have one git checkout in a build, then you’re fine.
> 
> If you have more than one git checkout in the same build, you need to organize them via codebases; this is the mechanism that buildbot uses to track multiple source repos in the same builder.
> 
> Jared
> 
>> On Nov 23, 2014, at 13:21, Vitali Lovich <vlovich at gmail.com> wrote:
>> 
>> Not using codebases due to other issues.  However, all of these source steps are for the same repository, so it shouldn’t matter here.
>> 
>> -Vitali
>> 
>>> On Nov 23, 2014, at 10:52 AM, Jared Grubb <jared.grubb at gmail.com> wrote:
>>> 
>>> Are you using the ‘codebases’ parameter? If you have multiple source steps in a build and you’re not using it, you will have collisions all over the place.
>>> 
>>> Jared
>>> 
>>>> On Nov 22, 2014, at 11:43, Vitali Lovich <vlovich at gmail.com> wrote:
>>>> 
>>>> Sorry.  What I wrote was a bit confusing.  Basically, the Git step always checks out the revision that was changed, even when I specify a specific branch.  I think it might have something to do with having multiple Git steps for the same repository?
>>>> 
>>>> Anyway, I have it working with shell commands.  I was just hoping to leverage the Git steps.
>>>> 
>>>>> On Nov 22, 2014, at 10:24 AM, Dustin J. Mitchell <dustin at v.igoro.us> wrote:
>>>>> 
>>>>> Is your 'workdir' step checking out *from* ../merge-dir?  That might
>>>>> be easiest with a basic shellcommand, yes.  But maybe I don't
>>>>> understand what you're trying to do.
>>>>> 
>>>>> Dustin
>>>>> 
>>>>>> On Mon, Nov 17, 2014 at 6:27 AM, Vitali Lovich <vlovich at gmail.com> wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> I’m wondering how I override the revision that git checks out?
>>>>>> The model I have set up is as follows:
>>>>>> merge-dir: checkout destination branch, merge in requested revision (i.e. revision property)
>>>>>> workdir: checkout merged result
>>>>>> 
>>>>>> The problem I’m having is that the Git step of workdir still always checks out the original revision.
>>>>>> I tried overriding ‘revision’ right before the Git step for workdir to no avail.  I tried setting got_revision,
>>>>>> but it looked to be ignored.
>>>>>> 
>>>>>> How do I go about having the Git step check out the revision I want instead of the revision it thinks I want?
>>>>>> Is falling back to command-line git the only way?
>>>>>> 
>>>>>> Thanks,
>>>>>> Vitali
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>>>>> Get technology previously reserved for billion-dollar corporations, FREE
>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
>>>>>> _______________________________________________
>>>>>> Buildbot-devel mailing list
>>>>>> Buildbot-devel at lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>>> Get technology previously reserved for billion-dollar corporations, FREE
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Buildbot-devel mailing list
>>>> Buildbot-devel at lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>> 
>> 
>