Multiple pipelines from a single Gitlab repository

Pipelines
1

I’d like to have one pipeline for master builds and one pipeline for feature branch builds so I can separate the stats for Speed and Reliability into master and non-master.

The current document suggests creating separate webhooks in Gitlab and says to follow instructions in the pipeline settings. But the pipeline settings for Gitlab repositories documents configuring a Gitlab Integration - which can only be done once.

What’s the current best practice for configuring multiple pipelines to be triggered from a single Gitlab repository?

2

Hey @uh-toby!

Thanks for the message - hope you are well :wave:

Since you mentioned that your seperate pipelines are using a different repository: the GitLab integration should meet what you are trying to achieve: you’d need to provide the Pipeline URL/Token to the Buildkite Integration in your GitLab repositories’ Settings.

Our integration supports just the one webhook per repository (as you’ve most likely found out). I could also get the integration looked at on our end for multiple webhook support in similar nature to GitHub also from a product lens.

Cheers

James

3

Hi James, sorry for the confusion - my pipelines will use the same repository.

Our integration supports just the one webhook per repository (as you’ve most likely found out). I could also get the integration looked at on our end for multiple webhook support in similar nature to GitHub also from a product lens.

I’d appreciate it if the integration could support multiple pipelines for a Gitlab repository. In the meantime could the documentation be updated?

4

No confusion at all! :slightly_smiling_face:

As of right now, as above - the native integration that Buildkite has as of now with GitLab can point to a single repository for a webhook - I’ll definitely raise this up with our integration folks to natively handle multiple webhooks per repository. Also docs alignment too

Cheers!

5

Hi @uh-toby , I am from the product team at Buildkite. Thanks for raising this with us. I am assuming that you have a monorepo setup is that correct?

This is the first time I am hearing of this gap with Gitlab, but usually in similar situations our customers get a starter pipeline that basically looks at what changed and then triggers separate pipelines from that initial pipeline that has the webhook trigger. Would that solve your problem also?

Thanks!

1 Like
6

Yes, we have a monorepo. Thanks, I think that will work for us.

1 Like