[Buildbot-devel] Gitlab hook module not present in 0.8.8?

John Carr johnmdcarr at me.com
Thu Mar 6 10:17:39 UTC 2014


o/ would be up for driving this

Sent from my iPhone

> On 6 Mar 2014, at 03:42, "Dustin J. Mitchell" <dustin at v.igoro.us> wrote:
> 
> It's in master (unreleased).  The /latest/ documentation documents
> master, while /current/ documents the most recent release (0.8.8).
> 
> It looks like the position of release driver for 0.8.9 is open, if
> someone would like to take those reins.  That would basically involve
> making a release branch, smoke testing it, and shepherding fixes into
> it.
> 
> Dustin
> 
>> On Wed, Mar 5, 2014 at 10:28 PM, shiny knight <theshinyknight at me.com> wrote:
>> Hi all
>> 
>> I am experimenting with Gitlab, since our company will move on it pretty soon. I have noticed that the docs mention gitlab hooks; altho it seems to not be working.
>> 
>> Following the instructions at this page:
>> 
>> http://docs.buildbot.net/latest/manual/cfg-statustargets.html
>> 
>> I have added to the status the
>> 
>> change_hook_dialects={ 'gitlab' : True}
>> 
>> And added on the gitlab settings/webhooks, the url as described
>> 
>> http://myserver:8010/change_hook/gitlab
>> 
>> But when I try to test the hook, the server return an error, saying that there is no gitlab module.
>> 
>> I thought that it was not possible, so I went in the Buildbot dir, and in fact, there is the github python file, but nothing about gitlab at all (not only in status.web.hooks but anywhere in the Buildbot directory. Went also to the buildbot installer dir, where I keep the original installer, and there is no trace of a py file for gitlab.
>> 
>> Is this an error of the installer? I use 0.8.8, which is the latest release that I see available for the master....tried to download it again and I stil see no gitlab.py file. Do I have to grab the file from some other place?
>> 
>> Thanks
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries.  Built-in WAN optimization and the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
> 
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works. 
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel




More information about the devel mailing list