[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines

[tomas.bjerr...@gmail.com (JIRA)]

Title: Message Title

Tomas Bjerre updated an issue   Jenkins / JENKINS-57390 Enable credentials in triggers using declarative pipelines Change By: Tomas Bjerre h1. Background This issue originates from this issue in Generic Webhook Trigger Plugin: [https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/107] The reporter is using declarative pipeline. The user wants to get the credential, secret text, and use it when configuring triggers. More specifically as value of the 'token' configuration parameter in the plugin. Something like this: {code:java} ...   environment {     JENKINS_TOKEN = credentials('JENKINS_TOKEN')   }        triggers {     GenericTrigger(      genericVariables: [        ...      ],      causeString: 'Triggered by $image',      token: env.JENKINS_TOKEN,      printContributedVariables: true,      printPostContent: true     )   } ... {code} h1. Problem The problem is that the credential, or variables form the environment block, is not available in the triggers block.   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199172.1557431690000.22474.1557431760106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.