[Buildbot-devel] Any way to specify revision with a Trigger step

[Amber Yust]

The Source steps are kind of special in that they specify their own
descriptions, which I believe overrides the description/descriptionDone
parameters. I'm not sure if there's an easy way to change that; subclassing
them might be a bit more involved than you're looking for.

~Amber

On Mon, Mar 28, 2011 at 4:44 PM, Matthew Morse <matt at apple.com> wrote:

> Amber,
>
> Thanks for the suggestion--it works great!
>
>
> builder_factory.addStep(
>         source.Git,
>         repourl= <some_url>,
>         branch='master',
>         submodules=False,
>         doStepIf= useLatestRevision,
>         alwaysUseLatest = True,
>         workdir="build",
>         haltOnFailure=True,
>     )
> builder_factory.addStep(
>         source.Git,
>         repourl= <some_url>,
>         branch='master',
>         submodules=False,
>         doStepIf= useCommitRevision,
>         alwaysUseLatest = False,
>         workdir="build",
>         haltOnFailure=True,
>     )
>
> One thing I'd like to improve it the labeling in the waterfall, to
> distinguish which step is being run and which one skipped. Right now it
> looks like:
>
>
>        ---------
>         update
>        skipped
>        ---------
>         update
>          stdio
>        ---------
>   <some prep step>
>        ---------
>         Build 7
>
> I'd like it to look like:
>
>        ---------
>  update from HEAD
>        skipped
>        ---------
>         update to
>    commit revision
>          stdio
>        ---------
>   <some prep step>
>        ---------
>         Build 7
>
>
> I've looked at the doc and tried adding a 'description' attribute, but that
> doesn't work--I'm clearly missing something. Any suggestions?
>
> Thanks,
> - Matt
>
>
>
>
> On Mar 22, 2011, at 7:25 PM PDT, Amber Yust wrote:
>
> You can use a separate source step triggered by a property+doStepIf that
> has alwaysUseLatest=True set.
>
> Your Triggerable scheduler can set the property that swaps which source
> step is active.
>
> ~Amber
>
> On Tue, Mar 22, 2011 at 6:45 PM, Matthew Morse <matt at apple.com> wrote:
>
>> Hi,
>>
>> I just subscribed to this list and have a question that I didn't see
>> answered in the archive.
>>
>> The problem is this:
>>
>> - We have multiple projects (A, B, and C), each in its own git repository
>> (Repo_A, Repo_B, Repo_C)
>>
>> - The projects are related. Specifically, the projects in B and C depend
>> on the project in A
>>
>> - We want a commit in Repo_A to trigger builds of A, B, and C.
>>
>> We have a GitPoller on Repo_A to trigger builds when there's a commit
>> there. Thereafter, we want to build B and C.
>>
>> The tricky part is that we want a commit to A (say, with SHA-1 hash
>> a2a1eb33d49...) to trigger builds of B and C at their HEAD versions. (Since
>> the repos are separate, the a2a1eb33d49... isn't relevant in Repo_B and
>> Repo_C.)
>>
>> I don't see a way to specify something like the HEAD revision when
>> configuring a Trigger.  Is that possible?  Alternatively, could it be done
>> in a Triggerable scheduler?  Other ideas?
>>
>> Thanks,
>> - Matt
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Enable your software for Intel(R) Active Management Technology to meet the
>> growing manageability and security demands of your customers. Businesses
>> are taking advantage of Intel(R) vPro (TM) technology - will your software
>> be a part of the solution? Download the Intel(R) Manageability Checker
>> today! http://p.sf.net/sfu/intel-dev2devmar
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110328/ab1de062/attachment.html>