|
||||||||||||||
|
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.
It seems to be a reasonable assumption that Jenkins has complete read+write access to a job's workspace. In most configurations, this should be a fatal error, as warnings would easily be missed unless reading the log, leading to difficult to investigate issues, incomplete artifacts, reports, etc.
Due to features like Wipe Out Workspace, the Workspace Cleanup Thread, and plugins such as SCM easily able to request a clean workspace, linking the entire file system from that appears to be a dangerous approach in general that maybe needs to be reconsidered.