Get a build status for a commit
Returns the specified build status for a commit.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”The commit’s SHA1.
The build status’ unique key
This can either be the repository slug or the UUID of the repository,
surrounded by curly-braces, for example: {repository UUID}.
This can either be the workspace ID (slug) or the workspace UUID
surrounded by curly-braces, for example: {workspace UUID}.
Responses
Section titled “ Responses ”The build status object with the specified key.
object
object
A link to a resource related to this object.
object
A link to a resource related to this object.
object
An identifier for the status that’s unique to its type (current “build” is the only supported type) and the vendor, e.g. BB-DEPLOY
The name of the ref that pointed to this commit at the time the status object was created. Note that this the ref may since have moved off of the commit. This optional field can be useful for build systems whose build triggers and configuration are branch-dependent (e.g. a Pipeline build). It is legitimate for this field to not be set, or even apply (e.g. a static linting job).
A URL linking back to the vendor or build system, for providing more information about whatever process produced this status. Accepts context variables repository and commit that Bitbucket will evaluate at runtime whenever at runtime. For example, one could use https://foo.com/builds/{repository.full_name} which Bitbucket will turn into https://foo.com/builds/foo/bar at render time.
Provides some indication of the status of this commit
An identifier for the build itself, e.g. BB-DEPLOY-1
A description of the build (e.g. “Unit tests in Bamboo”)
Example
{ "state": "FAILED"}If the repository is private and the request was not authenticated.
If the repository, commit, or build status key does not exist
Base type for most resource objects. It defines the common type element that identifies an object’s type. It also identifies the element as Swagger’s discriminator.
object
object
Optional structured data that is endpoint-specific.
object
Example generated
{ "type": "example", "error": { "message": "example", "detail": "example", "data": {} }}