Introduce new build status state: INCONCLUSIVE

XMLWordPrintable

      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

            Assignee:
            Unassigned
            Reporter:
            Piotr Swiecicki
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: