[users at bb.net] buildbot integration with gitlab

[Pierre Tardy]

Hi Gelonida,

Indeed, Buildbot supports this via gitlabstatuspush.

There is a "context" argument associated to a gitlab status push, which on
buildbot is configured by default with the builder name.
It can be any renderable so that can be a mixed of buildername +
properties, etc.

So I would advise to push as many status as you can to the SCM system as
this is what the developers want to see. IMHO people don't want to go to
buildbot UI to see their build status.

In the Buildbot own CI on github, we push 30 statuses. Github is nice
enough to just show only the failures, or a nice check icon saying all's
good if all's good.
I expect gitlab to do similar.


Pierre


On Mon, Mar 20, 2017 at 3:13 PM Gelonida <gelonida at gmail.com> wrote:

> Hi,
>
> Context:
>
> We're using Gitlab  for managing our merge requests.
>
>
> Problem:
>
> Gitlab allows CI pipelines, that can show a status icon next to a build
> request indicating, whether a merge requests passed CI tests or not.
>
> For one of our projects one of our colleagues added a small CI pipeline
> into gitlab (and one Runserver) and the status check is rather helpful
> for our development.
>
>
> We'd like to better integrate gitlab / buildbot.
>
> Question:
>
> How to best use gitlab together with buildbot and get the CI status back
> to gitlab?
>
> I assume, that I have to use the GitLabStatusPush object.
>
>
> What I'm not that sure about:
> - We have multiple builders for each repository /commit. How to decide,
> which builder / builders will update the status?
> - If there's multiple builders, will there be multiple statuses to be
> seen at gitlab?
>
>
> Thanks in advance for some answers / advice
>
>
>
>
>
>
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170320/79c81b6e/attachment.html>