Fixed and pushed.
2013/6/13 Kohsuke Kawaguchi <[email protected]> > 2013/6/12 Jesse Glick <[email protected]> > >> On 06/12/2013 09:38 AM, Kohsuke Kawaguchi wrote: >> >>> I don't think I can explain the difference between RUN_BUILDS permission >>> and BUILD >>> >>> someone having a permission to build a certain job and someone having a >>> permission to build in a certain slave feels symmetric to me. >>> >> >> It is not “symmetric” in the sense that the permission can be granted >> equivalently on either side; you need _both_ permissions. I am more >> concerned about the confusion resulting from one permission having two >> distinct meanings, each with a different scope (type of object). >> > > Perhaps the choice of the word wasn't very accurate, but I meant exactly > that you need both, and in that sense it's like two legs of our bodies. > > >> BUILD is also impliedBy UPDATE, which would make no sense for this new >> meaning. And its PermissionGroup, which unlike the PermissionScope cannot >> be a list, is Item.PERMISSIONS “Job”, rather than Computer.PERMISSIONS >> “Slave”. >> > > That's true. > > >> So I would still vote for a separate Computer.BUILD “Run Builds”. > > > OK. I'll update this accordingly this evening on the airplane. > > -- > Kohsuke Kawaguchi > -- 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.
