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

Commit da83990

Browse files
committed
doc
1 parent fbdec98 commit da83990

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

CHANGELOG.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,12 @@
22

33
Changelog of Pull Request Notifier for Bitbucket.
44

5+
## Unreleased
6+
### No issue
7+
doc
8+
9+
[fbdec988218c8d9](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/fbdec988218c8d9) Tomas Bjerre *2016-07-18 21:19:06*
10+
511
## 2.31
612
### GitHub [#131](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/issues/131) Buttons do not appear [4.3.1]
713
Making buttons compatible with 4.0.0 to 4.3.x

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -153,9 +153,11 @@ If you are using a CSRF protection in Jenkins, you can use the **Injection URL**
153153
* Set **Injection URL** field to `http://JENKINS/crumbIssuer/api/xml?xpath=//crumb/text()`. You may get an error like *primitive XPath result sets forbidden; implement jenkins.security.SecureRequester*. If so, you can set Injection URL to `http://JENKINS/crumbIssuer/api/xml?xpath=//crumb` in combination with regular expression `<crumb>([^<]*)</crumb>`. Or a third option is to checkout [this](https://wiki.jenkins-ci.org/display/JENKINS/Secure+Requester+Whitelist+Plugin) Jenkins plugin.
154154
* In the headers section, set header **.crumb** with value **${INJECTION_URL_VALUE}**.
155155

156-
## Issues
156+
## Reporting issues
157157
If things don't work as you expect, perhaps you should file an issue. But first, try troubleshooting it and provide as much info as possible. Here are some things that may help if added to an issue.
158158

159+
* Plugin version used.
160+
* Bitbucket Server version used.
159161
* Stack traces in Bitbucket Server log file.
160162
* Any browser console log messages, you can find it in Developer Tools in Chome by pressing F12.
161163
* Screenshot of plugin configuration in your issue.

0 commit comments

Comments
 (0)