|
||||||||
|
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/groups/opt_out.
For us its useless that i need to give job specuial names to be able to filter it for rights mangemnt. It feels like a bad work around to manage security/acess aspects via the job name.
For multi tenacy i need conatiners(like folder's) inside jenkins i can manage per client the rights for all the jobs inside it, no mater whats in there.
It shall also be impossible to access the filesystem outside the workspace of this container. AT the moment every job can access all files accessable by the user who is running jenkins process (on the master), that is npt acceptable from security perspective if you have one master managaging builds from different orgs. It's an overkill to have different jenkins server for different clients.
However we need to let different orgs let em manage their jobs (write config) and acceess each other jon's data inside the conatiner.