|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The only chance I see is that an extension to the ParameterDefinition type is introduced where the job context is passed upon instantiation. The ParameterDefinition is instantiated in the context of a job, so that should not be an issue. But overall that would require some change in the Jenkins internal APIs.
I think I will stick to manually setting the jobname in the System Groovy List Provider for now.