You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Webhook Pull Request Approved Event not triggering Jenkins MultiBranch Pipeline
but Pull Request Opened, ReOpened, ReScoped does triggered.
Do you know why?
This is hard to answer in detail as for me some more context is missing. In general I'd say it first of all makes sense to not trigger the Jenkins pipeline on PR approval (or decline). Question remains thought why you might think otherwise - or did I read that wrong?
This is my understanding:
Approving a pull-request does not change the contents/scope of the pull-request which is why there is no need to run the Jenkins pipeline again - it did already run on that revision.
Your mileage may vary thought. If you share a bit more of the context and what your motivation is, it might be possible to give better feedback and propose some more options.