Skip to content

Commit dc580a7

Browse files
author
Antonio Mansilla
authored
Merge pull request #29 from Flagbit/override-status-doc
Add documentation for overriding latest build status
2 parents 0f4ac95 + 207b2d0 commit dc580a7

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Bitbucket Cloud build status notifier plugin for Jenkins - [![Build Status][jenkins-status]][jenkins-builds]
22

33
Every time you trigger a build, you don't have to log in to your build server to see if it passed or failed. Now
4-
you will be able to know when your build is passing right within the Bitbucket UI.
4+
you will be able to know when your build is passing right within the Bitbucket Cloud UI.
55

66
Note: This plugin aims at the Atlassian-hosted BitBucket Cloud solution, not BitBucket Server (formerly known as Stash).
77

@@ -77,12 +77,13 @@ Third, you need to add the Bitbucket OAuth Consumer credentials. You have two wa
7777

7878
### Configure Jenkins to notify Bitbucket from a standard build
7979

80-
Once you have configured the credentials, configure jenkins to notify Bitbucket.
80+
Once you have configured the credentials, configure Jenkins to notify Bitbucket.
8181

8282
1. Go to the Job you want notifies the builds to Bitbucket.
8383
2. Click **Configure**.
8484
3. Select **Bitbucket notify build status**.
8585
4. Choose whether you want to notify the build status on Jenkins to Bitbucket.
86+
5. Choose whether given a same scm revision you want to notify a new build status for every job build or to override the latest one.
8687

8788
### Pipeline step to notify Bitbucket
8889

0 commit comments

Comments
 (0)