Skip to content
Switch branches/tags
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Brigade GitLab Gateway

Send GitLab events into a Brigade pipeline.

This is a Brigade gateway that listens to GitLab webhooks event stream and triggers events inside of Brigade.


  1. Have a running Kubernetes environment
  2. Setup Helm
  3. Setup Brigade core


From File

Clone Brigade GitLab Gateway and change directory

$ git clone
$ cd brigade-gitlab-gateway

Helm install brigade-gitlab-gateway

note name and namespace can be customized.

$ helm install --name gl-gw ./charts/brigade-gitlab-gateway

From Repo

Add this project as a helm repo

$ helm repo add glgw
$ helm install -n gl-gw glgw/brigade-gitlab-gateway

Building from Source

You must have the Go toolchain, make, and dep installed. For Docker support, you will need to have Docker installed as well. See more at Brigade Developers Guide From there:

$ make build

To build a Docker image

$ make docker-build


GitLab Gateway Brigade Core
v0.10.0 v0.10.0
v0.1.0 v0.9.0 (and previous)

GitLab Integration

The Default URL for the GitLab Gateway is at :7446/events/gitlab/. In your GitLab project, go to Settings -> Integrations. Depending on how you set up your Kubernetes and the GitLab Gateway will determine your externally accessable host/IP/Port. Out of the box the gateway sets up as LoadBalancer; use the host/Cluster IP and check the GitLab Gateway Kubernetes Service for the external port (something like 30001).

Enter that IP/Port and URL at the Webhook Integration URL. The Secret Token will be the same string used in the Brigade Project values.yaml sharedSecret property.

Check the boxes for the Trigger events to publish from the GitLab instance. SSL is optional.

Scripting Guide

tl;dr: GitLab Gateway produces 8 events: push, tag, issue, comment, mergerequest, wikipage, pipeline, build.


This project welcomes contributions and suggestions.