Open jmeit-fwdsec opened 1 year ago
1.: "Trigger not set" is written to the log for EVERY pipeline in Jenkins that is not configured for bitbucket (all other jobs in Jenkins).
2.: for OAuth consumer key, I could not get that to work. But what works is a decline like the approve I described here: https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin/issues/288#issuecomment-1306828733
for the decline look here: https://docs.atlassian.com/bitbucket-server/rest/5.16.0/bitbucket-rest.html#idm8287172368
and put that in the
post {
failure {
...
}
}
section
After making a PR on bitbucket, the plugin successfully starts a new build on Jenkins. After the build fails, the PR should be declined because I have ticked the box that says "Let Jenkins decline the pull request on BitBucket if the build fails".
The log shows that the webhook is working from bitbucket and then shows the payload that was received by Jenkins. Then it shows the following...
And it repeats "Trigger not set" many many times.
I have stored my OAuth consumer key as Secret Text, and selected it as the Credentials.
What more can I try?