Daniel Beck resolved Bug JENKINS-15397 as Incomplete

Report does not mention which Jenkins version this occurs with. Also, it's quite old by now, so closing this as incomplete. If it still occurs on recent Jenkins versions, feel free to reopen or file a new issue.

Also, answers to the following questions are also important for further investigation:

  • Are you trying to override the automatically created env variables manually, or do you mean they're not up to date?
  • How is the slave started?
  • Do you configure env variables in the node configuration?
  • Did you rename and/or change labels recently?
    • Did you afterwards not disconnect the slave?
  • How can this be reproduced?
    • Can it be reproduced in recent Jenkins versions?
Change By: Daniel Beck (21/May/14 3:40 PM)
Status: Open Resolved
Fix Version/s: current
Resolution: Incomplete
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/d/optout.

Reply via email to