PATH stuck on Windows slaves

[Simon Richter]

Hi,

I have a Windows slave attached to a master instance running on a Linux
system, and find that the PATH environment variable (or really, all
variables) get stuck at the value they are first seen at.

When I create a new environment variable in Windows and restart the
Jenkins service, the variable shows up both in the node overview and in
the builds. Deleting variables does not work, neither does changing.

When I delete and recreate the node in the master's setup, a fresh set
of environment variables is fetched.

Is this intentional? Can I somehow force a re-read?

Simon