[
https://issues.jenkins-ci.org/browse/JENKINS-12825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161060#comment-161060
]
Zachary Young commented on JENKINS-12825:
-----------------------------------------
I would like to see this also, with variable expansion in the list of WAR/EAR
files to be deployed such that it handles a list like 'foo.war, , baz.war'
correctly (the list in the configuration being '$deploy_foo, $deploy_bar,
$deploy_baz', and the user chose to leave the '$deploy_bar' variable empty to
omit it from the deployment).
> Allow expansion of environment variables in the configuration
> -------------------------------------------------------------
>
> Key: JENKINS-12825
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12825
> Project: Jenkins
> Issue Type: New Feature
> Components: deploy
> Reporter: hand_of_henry
>
> Ahoy,
> I'm creating a deployment build that's parameterized with a "Choice" pull
> down list. The goal is to deploy the war to the IP address specified by the
> build parameter. Currently the form fields do not resolve environment
> variables so the IP Address is never expanded to the selected value.
> I've tested this with a Tomcat 7 deploy and eyeballed the code and I don't
> see any resolving for any of the Tomcat Deployment Containers.
> I think this would be nice.
> Thanks,
> Brian
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
