[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers

[de...@ikedam.jp (JIRA)]

ikedam commented on JENKINS-17875 Make Jenkins environment variables available to dynamic providers It may be difficult to pass information about the current job to a groovy script. ParameterDefinition, which extensible-choice-parameter is based on,  has no interface to retreive information about the job it runs on. http://javadoc.jenkins-ci.org/hudson/model/ParameterDefinition.html Would you tell me why you want to get the job name, not just write it in the script? How about a following feature to meet your requirement? Groovy scripts in a system scope, that is, multiple jobs can share a same script. Just like Global Choice Parameter. Each job can pass its own parameter to the groovy script. In your case, pass the prefix of the name of jobs.  You must write the parameter value in the job configuration. It may be annoying when you create many jobs...

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.
For more options, visit https://groups.google.com/groups/opt_out.