|
||||||||
|
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.
I don't see how this would be helpful in any way.
Users who are able to configure jobs can just as easily write a shell script that cd's to the forbidden directory and then dumps data there. Or select a node you don't want them to select for their jobs.
There are countless potential issues with being able to configure jobs (and that's even assuming there were no arbitrary script execution issues in numerous plugins you may have installed!)
I'd really like to close this as Won't Fix since it simply wouldn't be an effective solution. Any objections?