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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've set up this new plugin to only allow merges to the master in case a certain Jenkins job has successfully built. Before that, I used the "minimum number of successful builds" which worked totally fine. But the problem with the new plugin is, that the successful build is not recognized even if it runs green.
Is there anything else one has to consider when adding the name of the Jenkins job which shall be successful before allowing the merge? I have added the name of the multibranch pipeline job directly, because it's located in the Jenkins root folder and not in any subfolder.
In the pull request under last builds I can also see that the status of this build is green, but the merge check still says that this job first has to be executed successfully for the latest build.
Hi Patrick,
I have encountered the same issue that you were having. Did you manage to find solution for this ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.