forked from jenkinsci/generic-webhook-trigger-plugin
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathISSUE_TEMPLATE
More file actions
26 lines (20 loc) · 1.23 KB
/
ISSUE_TEMPLATE
File metadata and controls
26 lines (20 loc) · 1.23 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
When reporting a bug, please **try** to provide as much information as possible.
* Plugin version used.
* Jenkins version used.
* Your configuration.
* Variables configured, names, expressions...
* Pipeline script (See Pipeline section in README)
* Build job log
* Post content received. It can be found in the job execution log. People using GitHub often forget to set the content type in "Manage webhook" when configuring the webhook at GitHub.
* A `curl` command and its response.
* Expected result and actual result.
You may also have a look at the test cases as they should answer the most common questions:
https://github.com/jenkinsci/generic-webhook-trigger-plugin/tree/master/src/test/resources/org/jenkinsci/plugins/gwt/bdd
If you are fiddling with expressions, you may want to checkout:
* [This JSONPath site](http://jsonpath.herokuapp.com/)
* [This XPath site](http://www.freeformatter.com/xpath-tester.html)
* [This regexp site](https://jex.im/regulex/)
A Curl command can look something like this:
```
curl -v -H "Content-Type: application/json" -X POST -d '{ "app":{ "name":"GitHub API", "url":"http://developer.github.com/v3/oauth/" }}' http://localhost:8080/jenkins/generic-webhook-trigger/invoke?token=sometoken
```