Branch based webhooks

Features
1

In my oppinion it would be awesome when we have branch based webhooks.
i.e. when merged into master fire webhook X, when merged into develop fire webhook Y

2

Thanks for the idea, i think a similar thing can be achieved when usin the templates in webhook.
So if you specify such endpoint http://my.server.com/${branch}/endpoint and let you endpoint decide what to do based on the branch variable, also this makes a multiple calls when pushed multiple branches at once (via Mercurial)

3

yeah something similar could be archived, but then you have i.e. a jenkins job failing, everytime it is not the specific branch.

Also it would reduce the workload on jenkins ( or other CI’s)

4

Ahh you want it for Jenkins, hmm that makes a lot of sense, CI integration is very important for us. We’ll definetly put this on a roadmap.

if the {branch} is used, then you shouldn’t have a failing jobs, you’ll simply define jobs accorind to Branches,

ie. /master/job1
/develop/job2

This means that every branch has it’s own job, that does different things.

1 Like
5

i acually never thought of this way! i’ll try it out!

6

Hi!

It’s finally this feature implemented?

Thanks!

7

Hi,

No, not yet however it’s going to be developed on 4.12 release together with a dedicated Jenkins plugin that allows CSRF workflows in jenkins

Best,