You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the new build status API that was added in Bitbucket Server 7.4. It differs from the old API in the following ways:
The old API is at /rest/api/1.0/build-status/latest/commits/{commitId}, and the new API is at /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits/{commitId}/builds.
What feature do you want to see added?
Use the new build status API that was added in Bitbucket Server 7.4. It differs from the old API in the following ways:
The old API is at /rest/api/1.0/build-status/latest/commits/{commitId}, and the new API is at /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits/{commitId}/builds.
The new {projectKey} and {repositorySlug} parameters would complicate fixing JENKINS-66620; see Send build completion notification for pull requests merged after build start bitbucket-branch-source-plugin#472 (comment).
The user of the old API only needs to be LICENSED. The user of the new API needs REPO_READ permission.
Build statuses that were added via the new API can be deleted later.
The plugin could then be changed to delete build statuses of aborted builds, as suggested in Send build completion notification for pull requests merged after build start bitbucket-branch-source-plugin#472 (comment).
Upstream changes
The text was updated successfully, but these errors were encountered: