Andrei Paun resolved Bug JENKINS-16625 as Fixed

This was actually a mistake I made. When I configured my slave I accidentally used Unix style separators when specifing the FS root where Jenkins projects should be deployed. It seems that Jenkins really trust the user and doesn't not validate that against the platform it runs so you might end up with your $WORKSPACE variable messed up.

Change By: Andrei Paun (04/Feb/13 3:09 PM)
Status: Open Resolved
Resolution: Fixed
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to