|
||||||||
|
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/d/optout.
I only used workspace as an example but I hear what you're saying and I agree that it's probably not the best idea to add support for it in this plugin.
My use case is actually a bit different. We use the dynamic parameter plugin and scriptler to allow users to select tags from git to include in a release bundle. In addition to this we would like to show which versions are actually deployed to production and stage next to the git tag drop down. So my hope was to use the EnvInject plugin and figure out the deployed versions (using a script) and put them as environment variables whose values would show up in the description field next to each drop down presented by the dynamic parameter plugin. But if the dynamic parameter plugin kicks in before EnvInject then it would still be impossible. The workaround we'll probably use is to present all production and stage versions in their own dropdown (populated by dynamic parameter choices (scripler)). Not quite as nice but at least I think it should work.
I still want to say that the Dynamic Parameter plugin (especially with the scriptler support) have helped us tremendously, so thank you very much.