-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Bitbucket Server
In Bitbucket Server, the list of pull requests does not show build statuses posted by Bitbucket Branch Source 930.ve6a_885b_3558f. However, the web pages of individual pull requests still show these build statuses. Earlier versions of Bitbucket Branch Source posted build statuses via a different REST API, and Bitbucket Server displayed those build statuses in both places.
The current build-status API (POST /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits/{commitId}/builds) was introduced in Bitbucket Server 7.4. It supports a "ref" property that specifies the branch that was built. Bitbucket Branch Source sets "ref" as null when it builds a pull request, and that prevents the build status from showing in the list of pull requests. The value of the "ref" property should instead name the source branch of the pull request, e.g. "refs/heads/myfeature".
This issue concerns compatibility between the Bitbucket Branch Source plugin and Bitbucket Server or Data Center.
- For the Bitbucket Server Integration plugin, see
JENKINS-74782instead. - For Bitbucket Cloud, see
JENKINS-75042andJENKINS-75015instead.
- causes
-
JENKINS-75116 Jenkins build notifications creates a new build state instead of updating the existing one on Bitbucket
- Closed
- relates to
-
JENKINS-74782 Bitbucket Server Integration plugin sends wrong ref to build status
- Resolved
- links to