Not compatible with the "Trigger builds remotely" configuration option

[raychinov]

• Jenkins 2.332.3
• Generic Webhook Trigger Version 1.85.2

When I enable Trigger builds remotely (e.g., from scripts) configuration in a Pipeline Jenkins job, Jenkins responses with HTTP 404 and:

{"jobs":null,"message":"Did not find any jobs with GenericTrigger configured! If you are using a token, you need to pass it like ...trigger/invoke?token=TOKENHERE. If you are not using a token, you need to authenticate like http://user:passsword@example.org/generic-webhook... "}

With no other changes, when disable the Trigger builds remotely config, the webhook trigger works as expected.

[tomasbjerre]

Here is the logic:

generic-webhook-trigger-plugin/src/main/java/org/jenkinsci/plugins/gwt/jobfinder/JobFinder.java

Line 108 in 8d66d67

return genericTokenNotConfigured && authenticationTokenMatches(authToken, givenToken)

So if you leave the token-field empty in the plugin configuration, and keep a token-value in Trigger builds remotely, it should work if you supply the token-value from Trigger builds remotely.

The first version of this plugin did not have its own token-field. It was added in #63 in 2018, perhaps it is time to simplify this code and just rely on the token-field from this plugin.

[tomasbjerre]

Support for BuildAuthorizationToken is dropped now in 2.0.0. The token used by this plugin now must be configured in the plugin config.