-
Type:
Improvement
-
Resolution: Duplicate
-
Priority:
Minor
-
Component/s: bitbucket-branch-source-plugin
-
None
Currently the text sent to Bitbucket as build status for a commit is hardcoded with messages that could be misleading (such as "This commit has test failures") if the job uses build statuses differently (i.e. UNSTABLE happens to mean something else). Â At the very least the text should say "The commit is unstable".
Â
if (Result.SUCCESS.equals(result)) { status = new BitbucketBuildStatus(hash, "This commit looks good", "SUCCESSFUL", url, key, name); } else if (Result.UNSTABLE.equals(result)) { status = new BitbucketBuildStatus(hash, "This commit has test failures", "FAILED", url, key, name); } else if (Result.FAILURE.equals(result)) { status = new BitbucketBuildStatus(hash, "There was a failure building this commit", "FAILED", url, key, name); } else if (result != null) { // ABORTED etc. status = new BitbucketBuildStatus(hash, "Something is wrong with the build of this commit", "FAILED", url, key, name); } else { status = new BitbucketBuildStatus(hash, "The tests have started...", "INPROGRESS", url, key, name); }
 Â
- duplicates
-
JENKINS-76027 Allow Bitbucket build status to be customised
-
- Fixed but Unreleased
-
- relates to
-
JENKINS-36755 Add the ability to switch off notifications.
-
- Resolved
-
-
JENKINS-35453 Allow disabling the default commit status notifier
-
- Resolved
-
-
JENKINS-65741 Add option to include a prefix to include the name of Bitbucket notification build status
-
- Closed
-