[Buildbot-devel] Change builder's build #'s to match subversion changeset #?

Amber Yust ayust at yelp.com
Wed Apr 27 20:18:03 UTC 2011


We've built something sort of like that at Yelp, but it's not inherently
tied into the BuildBot codebase - instead, certain build steps run scripts
that report results to a separate database, and we have a reporting/analysis
app that uses that results db to generate status information.

~Amber

On Wed, Apr 27, 2011 at 12:32 PM, Philippe McLean <philippe.mclean at gmail.com
> wrote:

> the environment on the build slave may also change between builds (for
> example a compiler upgrade), and this would difference would not be
> reflected in a build number based on svn revision. More modern source
> control systems (e.g. git/mercurial) also do not have sequential or small
> revision ids.
>
> A requirement that sometimes comes up, and does not seem to be met, is to
> generate globally unique build numbers, and associate them in some
> persistent database with the source revision id/ slave name / slave
> environment, so that builds can be tracked in the wild once they are
> released.
>
> e.g.
>
> fun-1.3-23433.exe
>
> is publicly released, and 23433 is the globally unique build number (not
> the builder's build number).
>
> has anyone built something like this?
>
> On Tue, Apr 26, 2011 at 6:42 PM, Charles Lepple <clepple at gmail.com> wrote:
>
>> On Apr 26, 2011, at 4:45 PM, William Deegan wrote:
>>
>> > Is there any way to modify the builder's build number to match the
>> > subversion changeset #?
>>
>> If the build number were assigned to be the Subversion revision
>> number, you would only be able to build each revision once before the
>> build number is no longer unique. (When bringing up a new builder for
>> NUT, I often end up resubmitting a build of one specific revision
>> several times before I get all of the dependencies right.)
>>
>> I'm not too familiar with that part of the code, but it might be tough
>> to pass the revision number through to the code that assigns the build
>> number (since got_revision is usually obtained through a build step
>> after the build begins). I guess you could look through the change
>> object, but this wouldn't be applicable if the build were triggered
>> from the "force build" button (as above), or from a periodic-type
>> scheduler.
>>
>> Can you describe your particular situation in more depth? If you are
>> looking for a more prominent SVN revision on the waterfall, you could
>> probably get that by subclassing the SVN step, and using the
>> got_revision property. The same would be true on a build status page,
>> although you would want a fallback in case the SVN step fails (network
>> trouble while checking out, etc).
>>
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> 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/20110427/0b2d4c2d/attachment.html>


More information about the devel mailing list