[Buildbot-devel] Triggered builds and git tags

Dan Kegel dank at kegel.com
Thu Apr 18 18:41:47 UTC 2013

It was a freshly added tag to a commit that had been there for a while.
I was rebuilding so the build script, which uses 'git describe' to
assign a version number, could get the new version number for the same
old bits.

On Thu, Apr 18, 2013 at 11:31 AM, Tim Hatch <tim at timhatch.com> wrote:
> Was this a brand new tag or an update?
> Tim
> Dan Kegel <dank at kegel.com> wrote:
>>FWIW, I noticed that if you have two tags at the same commit,
>>'git describe' will pick one of the two at random.
>>But I don't think that's what was happening here, all the tags on this
>>tree are distinct.
>>Hopefully it was just a brain fart.
>>On Tue, Apr 16, 2013 at 4:59 PM, Dustin J. Mitchell <dustin at v.igoro.us> wrote:
>>> On Tue, Apr 16, 2013 at 1:46 PM, Dan Kegel <dank at kegel.com> wrote:
>>>> I'm using Triggers to daisy chain a build between mac, windows, and linux,
>>>> which is working great except for one thing: git tag skew.
>>>> I pushed a tag manually, then did a force build at the start of the
>>>> chain, and the new tag was not
>>>> visible on the last machine in the daisy chain.
>>>> Forcing the build a second time worked fine; this time the tag propagated.
>>>> Is there some 'it's been too soon to do a git pull' timer I should be adjusting?
>>>> My tree stable timer is already set to 60 seconds.
>>> The tag wasn't available in *git*?  That sounds like a problem -
>>> propagation delay? - with your git server.
>>> Dustin
>>Precog is a next-generation analytics platform capable of advanced
>>analytics on semi-structured data. The platform includes APIs for building
>>apps and a phenomenal toolset for data science. Developers can use
>>our toolset for easy data analysis & visualization. Get a free account!
>>Buildbot-devel mailing list
>>Buildbot-devel at lists.sourceforge.net

More information about the devel mailing list