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

[Dustin J. Mitchell]

On Thu, Mar 6, 2014 at 11:50 PM, shiny knight <theshinyknight at me.com> wrote:
> I see, so there is a doc that document things that are yet to be released...that makes sense and explain why I was not able to find the py script.

Yeah, we try to be explicit about that in the root of the docs, and
/current/ is configured with a higher search rank, but .. c'est la
vie.

> Anyway I went ahead and got it from the repo; added in my hook dir for the 0.8.8 and it seems to work to a certain extent.
>
> When I use the "test hook" button on gitlab, the log show that the commits are received, altho nothing is displayed on the waterfall (not sure if this is expected or not; I can't see the source of what Gitlab send, nor I know what it send when you press that button).

Once the change is logged in twistd.log, it's up to the schedulers to
react to it, so that at least bisects the search space to find the
problem.

> While when I make a real commit, I see it on the waterfall page, but no builders are triggered (I have set as changesource only the PBChangeSource(), so I would expect that any change would trigger the builder); But I assume that this is just a misconfiguration that I did.
>
> Overall seems that the gitlab module works fine. Mostly is great to see an example of how it should look like...write one from scratch without even knowing how it works is quite a challenge.

Great!  Any additions to the docs will be most welcome:

https://github.com/buildbot/buildbot/blob/master/master/docs/manual/cfg-statustargets.rst#gitlab-hook

Dustin