Summary

Even though commits show successful builds, the Jenkins build key does not show up in the drop down when trying to configure Required Build merge check while using the Bitbucket Server Integration plugin.

Environment

Bitbucket Data Center and Server 7.14 +

Diagnosis

• Jenkins is integrated with Bitbucket using the Bitbucket Server Integration plugin.
• The Build section inside the Bitbucket Repository shows the Jenkins build running successfully.
  

• However when you try to add the Required Build merge check for the Repository it does not list the build key in the dropdown.
  

• When trying to check the Build key using the REST API $BITBUCKET_URL/rest/build-status/1.0/commits/{commitId} the key shows up as some numbers instead of build name/path configured in Jenkins.
  

Cause

• This is caused by older version of the Bitbucket Server Integration plugin.
  

Solution

• Upgrade the plugin to the latest version.
  

• Once the plugin is updated to the latest version, try pushing a new commit to trigger a new JOB. Now you can list the Build key in the dropdown when trying to configure Required Builds merge check in the Repository.
  

• Also the Build status API response for the commit will have the right Build key instead of numbers.