Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Duplicate
Fix Version/s: None
Component/s: Integration – Build Status
Labels:
None

Feedback Policy:

We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

According to https://developer.atlassian.com/bitbucket/server/docs/latest/how-tos/updating-build-status-for-commits.html
Bitbucket Server accepts only 3 possible outcomes from a build: INPROGRESS|SUCCESSFUL|FAILED.
Yet sometimes (e.g. build is cancelled, agent was taken down, etc.) the outcome is INCONCLUSIVE - it's neither success or fail, it's not in progress either.

Some may argue such state should be represented as FAILED, but we have requests to distinguish INCONCLUSIVE from FAILED outcome, see ~~BAM-18089~~

Attachments

Issue Links

blocks

BAM-18089 Cancelled build is shown as error in BitBucket Server

Closed

duplicates

BSERV-3219 Add 'Canceled' state for Build Statuses

Gathering Interest

is duplicated by

BSERV-10651 Add more build status states to Bitbucket

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...

(1 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Piotr Swiecicki

Votes:: 2 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 20/Dec/2016 2:31 PM

Updated:: 19/Sep/2019 5:49 AM

Resolved:: 15/Oct/2018 8:54 PM