Hi,
I am not a Jenkins expert, but as far as I know (and I remember to read this somewhere in either Jenkins documentation or on some forum), this is by design behavior that Jenkins runtime cannot access anything out of the workspace folder border. Which means that *everything* accessed by Jenkins runtime *must* be within the workspace of the given project. (And even in this case, you should not rely on the absolute paths but may use only relative ones because I seem to remember that I saw that Jenkins may put something into dynamic temporary folder and execute it from there.) Obviously, processes started by Jenkins are not limited to its workspace and can access resources outside of it.
