I thought more about this, and I still think the BUILD permission is appropriate. I don't think I can explain the difference between RUN_BUILDS pemission and BUILD permission --- someone having a permission to build a certain job and someone having a permission to build in a certain slave feels symmetric to me.
PermissionScope is a good catch indeed, but a Permission can belong to multiple PermissionScopes, so we just need to make the BUILD permission belong to both. 2013/6/12 Jesse Glick <[email protected]> > I think you must, because BUILD (which is defined in Item BTW, not > AbstractProject) uses PermissionScope.ITEM, whereas you need something in > COMPUTER. > > When you fix this, cloudbees-folders-plus will be obsolete: you will just > use regular RBAC to define a Group on the Node with the new > RUN_BUILDSpermission (or whatever you call it), and make sure the > Authentication associated with some folder (or individual job) is a > member of that group. > > — > Reply to this email directly or view it on > GitHub<https://github.com/jenkinsci/jenkins/commit/ada4a21607766d23347b927b49ccfa272d685ae7#commitcomment-3406835> > . > -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
