[
https://issues.jenkins-ci.org/browse/JENKINS-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kohsuke Kawaguchi resolved JENKINS-9899.
----------------------------------------
Resolution: Won't Fix
I doubt if such a check is useful because once the build starts, you can always
just cd into any directories that other builds own.
To do this kind of isolation you need a lot more than just a check inside
Jenkins.
If you do something like that for a specific environment, I also wonder if
{{ItemListener.onUpdated()}} is a sufficient hook to implement it all in a
plugin.
> Permissions check of custom workspace
> -------------------------------------
>
> Key: JENKINS-9899
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9899
> Project: Jenkins
> Issue Type: New Feature
> Components: core
> Reporter: vjuranek
>
> Implement a check if custom workspace can point into specified directory -
> e.g. check if it points to another workspace which is inaccessible for the
> user due to Project-based Matrix Authorization Strategy setup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
