Refering to violation comments to bbs for job DSL

tomasbjerre · Mar 18, 2017 · 85aabe1 · 85aabe1
1 parent 1f8a72d
commit 85aabe1
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,7 +2,12 @@
 
 Changelog of Pull Request Notifier for Bitbucket.
 
-## Unreleased
+## 2.60
+### GitHub [#197](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/issues/197) Button not displaying on PRs which are merged
+  Adding previously uncommitted change for
+
+  [ba712899a44e6f8](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/ba712899a44e6f8) Tomas Bjerre *2017-03-07 16:30:56*
+
 ### No issue
   doc
 

diff --git a/README_jenkins.md b/README_jenkins.md
@@ -6,6 +6,8 @@ The job that you want to trigger must have:
  * *Trigger builds remotely* checkbox checked.
   * You may, or may not, use a token here.
 
+There is a full job-dsl for this in [here](https://github.com/jenkinsci/violation-comments-to-stash-plugin).
+
 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.
 
 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.