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.
Bitbucket provides required build options to allow specific branches to have successful build before they can be merged. It requires a build key that is the name of the job. However, I can't seem to find the right build key as they job is successful but bitbucket still doesn't allow the merge to happen.
We have the same issue.
We have a mulitbranch pipeline and I cannot get it to match any of the Jenkins build keys.
It always tells me that there is a build needed, no matter what I give as key.
I have tried to far:
<project>
<project>/
<project>/*
<project>/<pipeline>
<project>/job/<pipeline>
<project>/<branch>/<pipeline>
nothing works.
Hi Tomas,
I have set up Bitbucket and Jenkins on virtual machine with integration using Bitbucket server integration plugin and managed to get the required-build to work. The build key is simply the job name. If the job is in folder you must include folder name. However, still having issue to get this to work on the organisation env. Investigating how to resolve it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.