|
||||||||
|
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/groups/opt_out.
Maybe someone is interested in the usecase of the scenario described above:
We are using homogeneous maven commands for all maven jobs that are based on company standard. Additionally these jobs are created from a template where the global environment variables are configured. Now and then a developer needs additional parameters added to the standard maven command. With Hudson I defined a placeholder environment variable without a value, the developer did an overwrite of this variable on his maven job. With Jenkins overwriting an environment variable does not work. I deleted the placeholder from the global environments an got the error message that is base to this issue because the placeholders are not configured in every job.