Skip to content

Commit 7506f12

Browse files
committed
Updated readme with new options
1 parent 8dc6c98 commit 7506f12

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -60,14 +60,16 @@ Select *Stash Pull Request Builder* then configure:
6060
- Only build when asked (with test phrase):
6161
- CI Build Phrases: default: "test this please"
6262
- Target branches: a comma separated list of branches (e.g. brancha,branchb)
63+
- Approve PR on build success: marks a pull request as Approved with the specified user. Make sure the user has sufficient rights to update the status of pull requests and the username is "slugified".
64+
- Mark PR with Needs Work on build failure: As above, but with failed builds. The same user requirements apply.
6365

6466
## Building the merge of Source Branch into Target Branch
6567

6668
You may want Jenkins to build the merged PR (that is the merge of `sourceBranch` into `targetBranch`) to catch any issues resulting from this. To do this change the Branch Specifier from `origin/pr/${pullRequestId}/from` to `origin/pr/${pullRequestId}/merge`
6769

6870
If you are building the merged PR you probably want Jenkins to do a new build when the target branch changes. There is an advanced option in the build trigger, "Rebuild if destination branch changes?" which enables this.
6971

70-
You probably also only want to build if the PR was mergeable and always without conflicts. There are advanced options in the build trigger for both of these.
72+
You probably also only want to build if the PR was mergeable and always without conflicts. There are advanced options in the build trigger for both of these.
7173

7274
**NOTE: *Always enable `Build only if Stash reports no conflicts` if using the merge RefSpec!*** This will make sure the lazy merge on stash has happened before the build is triggered.
7375

0 commit comments

Comments
 (0)