doc

jenkinsci · Jul 16, 2017 · 0cda563 · 0cda563
1 parent edcfb9d
commit 0cda563
Show file tree

Hide file tree

Showing 5 changed files with 12 additions and 300 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,10 +5,19 @@ Changelog of Violation Comments to Bitbucket Server Plugin.
 ## Unreleased
 ### No issue
 
+**doc**
+
+
+[80a7501862e1aec](https://github.com/jenkinsci/violation-comments-to-stash-plugin/commit/80a7501862e1aec) Tomas Bjerre *2017-07-15 13:47:47*
+
+
+## 1.51
+### No issue
+
 **Violations-lib 1.29 with reporter field**
 
 
-[4c7a4dbd799175c](https://github.com/jenkinsci/violation-comments-to-stash-plugin/commit/4c7a4dbd799175c) Tomas Bjerre *2017-07-15 13:37:30*
+[a20cf15a3c0d32b](https://github.com/jenkinsci/violation-comments-to-stash-plugin/commit/a20cf15a3c0d32b) Tomas Bjerre *2017-07-15 13:45:13*
 
 **Updating doc on Infer**
 

diff --git a/README.md b/README.md
@@ -291,9 +291,8 @@ More details on Jenkins plugin development is available [here](https://wiki.jenk
 
 There is a ```/build.sh``` that will perform a full build and test the plugin.
 
-Some tests are implemented in maven project in ```/plugin-test```. This is to avoid classpath issues with the plugin. These are web tests that will start Jenkins with the plugin on localhost and perform some configuration tests.
+If you have release-permissions this is how you do a release:
 
-A release is created like this. You need to clone from jenkinsci-repo, with https and have username/password in settings.xml.
 ```
 mvn release:prepare release:perform
 ```