[
https://issues.jenkins-ci.org/browse/JENKINS-13843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163066#comment-163066
]
Julian Taylor commented on JENKINS-13843:
-----------------------------------------
I finally got around to restarting my jenkins.
The weird behavior is indeed caused by the OS environment variable on the
master.
if I start the master with this variable unset the problem does not occur.
> envionment variable from label expression, inconsistent casing on nodes
> -----------------------------------------------------------------------
>
> Key: JENKINS-13843
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13843
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Reporter: Julian Taylor
> Priority: Minor
> Attachments: config.xml
>
>
> when using a label expression named "os" the environment variable in a shell
> on the local master node is $OS but on slave nodes it is $os
> maybe there is some weird interaction with the $OS environment variable which
> is defined in the shell that started jenkins (set to Linux), and not present
> on the slave nodes.
--
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
