Skip to content
This repository was archived by the owner on Jun 9, 2021. It is now read-only.

Commit 85aabe1

Browse files
committed
Refering to violation comments to bbs for job DSL
1 parent 1f8a72d commit 85aabe1

File tree

2 files changed

+8
-1
lines changed

2 files changed

+8
-1
lines changed

CHANGELOG.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,12 @@
22

33
Changelog of Pull Request Notifier for Bitbucket.
44

5-
## Unreleased
5+
## 2.60
6+
### GitHub [#197](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/issues/197) Button not displaying on PRs which are merged
7+
Adding previously uncommitted change for
8+
9+
[ba712899a44e6f8](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/ba712899a44e6f8) Tomas Bjerre *2017-03-07 16:30:56*
10+
611
### No issue
712
doc
813

README_jenkins.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ The job that you want to trigger must have:
66
* *Trigger builds remotely* checkbox checked.
77
* You may, or may not, use a token here.
88

9+
There is a full job-dsl for this in [here](https://github.com/jenkinsci/violation-comments-to-stash-plugin).
10+
911
I like to add an *Execute shell* build step and then just do `echo param: $paramName` to test that my parameter shows up in the build job log.
1012

1113
First, you may try to trigger Jenkins with [Curl](https://github.com/curl/curl) from command line and then, when you know how it should be done, configure the plugin.

0 commit comments

Comments
 (0)