|
||||||||
|
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/d/optout.
The proposed change will not help. For the specified example:
Captured group will be ${ENV:INSTALL_DIR which will not be parsed by replaceVars as you expect.
I see the support for nested expressions as a bad idea - it would be even possible to run into endless recursion if it is not done right.
What do you think if we allow constructs like:
${FILE:ENV:SOMEVAR}
which will be resolved into file content of the specified file?