-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Windows Server 2008, Tomcat 6, Java 6, Novell LDAP
I sucessfully added (peopele icon is displayed and user from this group can log in) a group to Hudson Main Configuration User Managment.
All users from this group are not added also as person and are only present via the group membership.
I give the group all rights in project-matrix based table except Administer.
I create a job with default (no user, no groups in it, except Anonymous with no rights).
Now i log in as a member of this group and change into the new job.
I can view the job cfg but not edit/configure it, i can't run the job!
I gave the group global rights to configure jobs and Build jobs, so why is it not possible?
I also tried a variant:
I create a job and add the group with all rights except "Delete".
Same problem as above.
How is this thought to be used/working?
At the moment the project based rights cover with global rights per project.
For efficient use of groups and master adminsration i would except that global rights to groups shall out number project based group cfg.
How is this thought to be used/working?