Chaitanya Prakash Bapat
1 min readMar 3, 2020

--

Hey Prashant, Thanks a lot for this blog.

However 1 question

I tried using 2 Github webhooks

1 webhook between Github Jenkins

2nd webhook between Github and Lambda function.

That lambda function is responsible for triggering the Jenkins.

We have a multi-branch pipeline (more than 7–8 branches)

But unfortunately, even if I trigger different branches(jobs), on Github UI side all of them are reported at just 1 place

continuous-integration/jenkins/pr-merge

Any idea how to ensure they are reported as separate on Github UI too?

Googling it reveals this continuous-integration/jenkins/pr-merge is used when Discover strategy = “Discover pull requests from origin” and “Discover pull requests from forks” both set to “merging the pull request with the current target branch revision”

But not sure how to fix it.

--

--

Chaitanya Prakash Bapat
Chaitanya Prakash Bapat

Written by Chaitanya Prakash Bapat

Music, Sports and Data. Apache committer @ Apache MXNet | Ex- Amazon | GaTech

No responses yet