Can we use environment variables in regexpFilterExpression? about generic-webhook-trigger-plugin HOT 6 CLOSED

Here is a working example of that: https://github.com/jenkinsci/generic-webhook-trigger-plugin/blob/master/sandbox/sandbox.jenkinsfile

from generic-webhook-trigger-plugin.

It's working now. Thanks!

from generic-webhook-trigger-plugin.

no problem!

from generic-webhook-trigger-plugin.

@tomasbjerre
im trying the environment variable substitution on a declarative pipeline but it doesnt seem to work any suggestions?

 regexpFilterText: '$ref $changed_files $commit_user',
 regexpFilterExpression: "^refs/heads/${env.BRANCH_NAME}\\s(.*\"(${params.BRAND}\\/params.yml).*\"|.*\"(${params.BRAND}\\/.*\\.properties).*\")[^\\s]+?\\s((?!${env.GIT_USER}))"

The variable are part of environment{} in the pipeline template.

from generic-webhook-trigger-plugin.

You should open a new issue about that. And explain how you are using the plugin so that there is something to investigate.

from generic-webhook-trigger-plugin.

I am trying to set a dynamic filter based on the repo and the job name (we use same Jenkinsfile in all the repos) with following settings:

regexpFilterText: '$repo',
regexpFilterExpression: '/${env.JOB_NAME}.split("/")[1]/g'

The $repo is correctly set to the repo name e.g. template-service and I want to match it with the repo name in the job e.g. ORG/template-service/master. Even with this filter, the webhook is triggering all the jobs. I tried changing '${env.JOB_NAME}' to 'env.JOB_NAME' but that does not work either. Is it possible to use environment variables in regexpFilterExpression? Why is this filter triggering all the jobs?

@ajaypandit can you share the code

It's working now. Thanks!

@ajaypandit Could you please share your worked code? I have the similar issue. Thanks so much.

from generic-webhook-trigger-plugin.