|
||||||||
|
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.

Gregory,
variables are a confusing lot in Jenkins, since there is a lot of variation among plugins and the ways they are handled. I try to use the java property style with dots to group properties.
The simplest example I came up with is the following:
The parameterized build trigger plugin can handle the same situation. I'm not sure on 'execute shell' build step, since I have not used it before. Maybe it is possible to have a duplicate variable which replaces the dot for an underscore. I saw the build-name-setter plugin use another way: ${ENV,var="VARIABLENAME"}.
With kind regards,
Joris