Webhooks branch filtering

Just a feature that I'd find useful: I have a web hook that is triggered on Push events, however I only want it to be triggered for pushes to a specific branch(s). When creating a webhook, it could be possible to select the branches where the webhook would be triggered.

Perhaps even having some kind of regex matching so that for instance, all branches following feature/* would trigger a certain webhook.

I have found gitlabhq/gitlabhq/issues/1176, but there was no answer at the time.

Thanks,

Added gitlab-foss14213 gitlab-foss13239 labels

yes. this is absolutely needed feature. especially for CI/CD systems, that start deploy on webhook. any change in any branch triggers redeploy because there is no possibility to set a hook only for master push. very annoying (

Any progress on this? According to https://github.com/gitlabhq/gitlabhq/issues/1176 this is affecting quite a few users...

+1

+1

I've labelled this as Platform in GitLab FOSS, but might be ~CI related? (https://gitlab.com/gitlab-org/gitlab-ce/issues/20338#note_17148232)

added ~480950 label

changed milestone to %Backlog in gitlab-foss

Yes this would be very useful! +1

Yes definitely needed +1

+1

+1

+1

added ~123454 label

+1

/cc @mydigitalself

mentioned in issue gitlab-foss#17457 (moved)

added shortlist in GitLab FOSS label

+1

Being able to set webhooks to branches is important for our automated deployments....we were investigating complicated work arounds until I saw this as a request.

+1

What would it look like in the UI?
Would it be similar to the protected branches UI with wildcards?

/cc @tauriedavis, @dimitrieh

added ~19492 label

Issues that need gitlab-foss2024184 should not be labeled with gitlab-foss1890178 so I've removed this.

cc @mydigitalself for possible scheduling.

removed ~123454 label

+1

+1

+1

+1

Please please please escalate this. Larger scale projects become too noisy without branch filtering. +1

Pls, it's 2017.

+1

+1

cc @dimitrieh @markpundsack @mydigitalself Largely asked for feature. Lets get this started so we can add it to an upcoming release.

We need to do some pretty significant overhauling of our integrations & hooks. I absolutely want to do this in the future, but it would probably be a little later in the year, but it's certainly on my shortlist in GitLab FOSS to schedule. We have a lot of performance-related work and some EE related work in priority right now, but will certainly look at this in the summer.

mentioned in issue gitlab-foss#32925 (closed)

Maybe this is the correct feature or maybe there is some intermediate work around.

I'm looking for 2 possible webhook/trigger/something.

1. Push to X branch -> Run Pipeline (.gitlab-ci.yml already doing this) -> Open MR for X branch to Y branch (in some cases this is master, in some cases this is dev) -> Run Pipeline (.gitlab-ci.yml already doing this upon commit) -> Merge if Pipeline succeeds -> Close MR -> Possibly Delete branch (since the functionality is based on the X branch if it needs to remain that can be done).

or

2. Push to X branch -> Run Pipeline -> Open MR -> Run Pipeline -> (manually accept MR if build succeeds)

+1

+1

+1

+1

+1

+1

+1

+1

+1

@markglenfletcher would you be able to provide some insight here? I know we briefly discussed in gitlab-foss#14646 (moved)

changed milestone to %Next 2-3 months in gitlab-foss

+1 i think is the right moment resovl this

is a great missing feature. Now for every push in every branch, the pipeline is triggered.

Maybe we can squeeze this into 10.1 @mydigitalself?

moved from gitlab-foss#20338 (moved)