A token was supplied.\nIf you are using a token, you need to pass it like ...trigger/invoke?token=TOKENHERE\nIf you are not using a token about generic-webhook-trigger-plugin HOT 7 CLOSED

yes, I set a 60 min as ttl.

That means you have to disable the cache, wait up to 60 minutes or restart Jenkins.

from generic-webhook-trigger-plugin.

Closing this issue because there is nothing in it that can be investigated. Open new issue and provide your exact configuration as asked for in the issue template.

from generic-webhook-trigger-plugin.

pipeline：

pipeline {
    agent any
    triggers {
        GenericTrigger(
             genericVariables: [
                 [key: 'ref', value: '$.ref'],
                 [key: 'before', value: '$.before'],
                 [key: 'after', value: '$.after']
             ],
             causeString: 'Triggered on $ref',
             token: '12345678',
             printContributedVariables: true,
             printPostContent: true
        )
    }
    stages {
        // your stages here
    }
}

The free-style configuration is normal.

from generic-webhook-trigger-plugin.

I recently updated the plugin to the 2.1.1 version and new jobs created after the plugin update are not triggered by the plugin.
The plugin response is the same that @cf1998 mentioned:

{"jobs":null,"message":"Did not find any jobs with GenericTrigger configured!\nA token was supplied.\nIf you are using a token, you need to pass it like ...trigger/invoke?token=TOKENHERE\nIf you are not using a token, you need to authenticate like http://user:[email protected]/generic-webhook...\n"}

I must say that older jobs created before the plugin update work fine, the problem is with the new ones.
The only way I managed to get the new ones working was restarting jenkins. No new created job will be triggered without restarting Jenkins.

from generic-webhook-trigger-plugin.

Are you using the cache?

from generic-webhook-trigger-plugin.

yes, I set a 60 min as ttl.

from generic-webhook-trigger-plugin.

Perfect, I will check that.

Thank you for the quick response!

EDIT:
@tomasbjerre that was it. Waiting for the cache to be invalid do the trick.

from generic-webhook-trigger-plugin.