Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Hudson-ci/features/Team Concept"
m (New page: Feature: Team concept The idea is to implement the concept of team so that several authentication and authorization can be assigned to that team. This helps multiple software project t...) |
|||
| Line 1: | Line 1: | ||
| − | + | The idea is to implement the concept of team so that several authentication and authorization can be assigned to that team. This helps multiple software project teams can use a single Hudson, but each team won't mess with other teams jobs | |
| − | + | The tasks are<br> | |
| − | + | Implement the concept of System admin and team admin | |
| − | + | *System admin are responsible for | |
| − | + | ||
| − | + | #Setting up team and adding a team admin | |
| − | + | #Hudson wide Authentication | |
| − | + | #Other higher level administration like installing plugin | |
| − | + | #Assign public jobs (with no associated teams) to specific teams | |
| − | + | #Every hudson will have at least System admin | |
| − | + | #Team admin has less power | |
| − | + | #Every team will have at least one team admin | |
| − | + | #Add and remove team members | |
| − | + | #Authorize user permission such as which member can edit job, delete job etc | |
| − | + | #Team member | |
| − | + | #Can create and configure job if team admin admits | |
| − | + | #Can set a job as public so that other teams can see it | |
| − | + | #Can delete any job if team admin admits or only delete the self created job | |
| − | + | #Can delete any job builds if team admin admits or only delete the self created job builds | |
| − | + | #Can run any team job and public job | |
| − | + | ||
| − | + | *Implement Permisson Scheme | |
| − | + | ||
| − | + | #System Admin Permission | |
| − | + | #Team Admin Permission | |
| − | + | #Team Member Permission | |
| − | + | ||
| − | + | *Implement the concept of Groups | |
| − | + | ||
| − | + | #group can have any user as member | |
| − | + | #Any group can be assigned with certain permission | |
| − | + | #(Ex. system-admin group can be assigned with System Admin permission ) | |
| − | + | ||
| − | + | *Implement the concept of job permission | |
| − | + | ||
| − | + | #Global jobs - any one can view | |
| − | + | #Team jobs | |
| − | + | #Only team members can view team private jobs | |
| − | + | #Only certain team members can manually run | |
| + | #Only certain team members can edit configuration | ||
| + | #Only certain team members can delete job | ||
| + | #Only certain team members can delete job build | ||
| + | |||
| + | *Implement project view based on team authorization | ||
| + | |||
| + | #Particular team can only view their jobs and any public jobs | ||
| + | #Anonymous users can view jobs only allowed to view as public<br><br> | ||
Revision as of 17:44, 15 February 2013
The idea is to implement the concept of team so that several authentication and authorization can be assigned to that team. This helps multiple software project teams can use a single Hudson, but each team won't mess with other teams jobs
The tasks are
Implement the concept of System admin and team admin
- System admin are responsible for
- Setting up team and adding a team admin
- Hudson wide Authentication
- Other higher level administration like installing plugin
- Assign public jobs (with no associated teams) to specific teams
- Every hudson will have at least System admin
- Team admin has less power
- Every team will have at least one team admin
- Add and remove team members
- Authorize user permission such as which member can edit job, delete job etc
- Team member
- Can create and configure job if team admin admits
- Can set a job as public so that other teams can see it
- Can delete any job if team admin admits or only delete the self created job
- Can delete any job builds if team admin admits or only delete the self created job builds
- Can run any team job and public job
- Implement Permisson Scheme
- System Admin Permission
- Team Admin Permission
- Team Member Permission
- Implement the concept of Groups
- group can have any user as member
- Any group can be assigned with certain permission
- (Ex. system-admin group can be assigned with System Admin permission )
- Implement the concept of job permission
- Global jobs - any one can view
- Team jobs
- Only team members can view team private jobs
- Only certain team members can manually run
- Only certain team members can edit configuration
- Only certain team members can delete job
- Only certain team members can delete job build
- Implement project view based on team authorization
- Particular team can only view their jobs and any public jobs
- Anonymous users can view jobs only allowed to view as public