Notice: This Wiki is now read only and edits are no longer 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"
| Line 3: | Line 3: | ||
The tasks are<br> | The tasks are<br> | ||
| − | Implement the concept of System admin and team admin | + | Implement the concept of System admin and team admin |
*System admin are responsible for | *System admin are responsible for | ||
| − | #Setting up team and adding a team admin | + | #Setting up team and adding a team admin |
| − | #Hudson wide Authentication | + | #Hudson wide Authentication |
| − | #Other higher level administration like installing plugin | + | #Other higher level administration like installing plugin |
| − | #Assign public jobs (with no associated teams) to specific teams | + | #Assign public jobs (with no associated teams) to specific teams |
| − | #Every hudson will have at least System admin | + | #Every hudson will have at least System admin |
| − | #Team admin has less power | + | #Team admin has less power |
| − | #Every team will have at least one team admin | + | #Every team will have at least one team admin |
| − | #Add and remove team members | + | #Add and remove team members |
| − | #Authorize user permission such as which member can edit job, delete job etc | + | #Authorize user permission such as which member can edit job, delete job etc |
| − | #Team member | + | #Team member |
| − | #Can create and configure job if team admin admits | + | #Can create and configure job if team admin admits |
| − | #Can set a job as public so that other teams can see it | + | #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 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 delete any job builds if team admin admits or only delete the self created job builds |
#Can run any team job and public job | #Can run any team job and public job | ||
*Implement Permisson Scheme | *Implement Permisson Scheme | ||
| − | #System Admin Permission | + | #System Admin Permission |
| − | #Team Admin Permission | + | #Team Admin Permission |
#Team Member Permission | #Team Member Permission | ||
*Implement the concept of Groups | *Implement the concept of Groups | ||
| − | #group can have any user as member | + | #group can have any user as member |
| − | #Any group can be assigned with certain permission | + | #Any group can be assigned with certain permission |
#(Ex. system-admin group can be assigned with System Admin permission ) | #(Ex. system-admin group can be assigned with System Admin permission ) | ||
*Implement the concept of job permission | *Implement the concept of job permission | ||
| − | #Global jobs - any one can view | + | #Global jobs - any one can view |
| − | #Team jobs | + | #Team jobs |
| − | #Only team members can view team private jobs | + | #Only team members can view team private jobs |
| − | #Only certain team members can manually run | + | #Only certain team members can manually run |
| − | #Only certain team members can edit configuration | + | #Only certain team members can edit configuration |
| − | #Only certain team members can delete job | + | #Only certain team members can delete job |
#Only certain team members can delete job build | #Only certain team members can delete job build | ||
*Implement project view based on team authorization | *Implement project view based on team authorization | ||
| − | #Particular team can only view their jobs and any public jobs | + | #Particular team can only view their jobs and any public jobs |
| − | #Anonymous users can view jobs only allowed to view as public | + | #Anonymous users can view jobs only allowed to view as public |
| + | |||
| + | === Capabilities === | ||
| + | |||
| + | {| width="800" border="1" cellpadding="1" cellspacing="1" | ||
| + | |- | ||
| + | | Capability | ||
| + | | System Admin | ||
| + | | Team Admin | ||
| + | | Team Member | ||
| + | |- | ||
| + | | See team job | ||
| + | | All | ||
| + | | Team | ||
| + | | Team | ||
| + | |- | ||
| + | | Create team job | ||
| + | | All | ||
| + | | Team | ||
| + | | <Team> | ||
| + | |- | ||
| + | | Delete team job | ||
| + | | All | ||
| + | | Team | ||
| + | | Self-created or <Team> | ||
| + | |- | ||
| + | | Configure team job | ||
| + | | All | ||
| + | | Team | ||
| + | | Self-created or <Team> | ||
| + | |- | ||
| + | | Run team job | ||
| + | | All | ||
| + | | Team | ||
| + | | Self-created or <Team> | ||
| + | |- | ||
| + | | Set team job public | ||
| + | | All | ||
| + | | Team | ||
| + | | <Team> | ||
| + | |} | ||
Revision as of 23:03, 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
Capabilities
| Capability | System Admin | Team Admin | Team Member |
| See team job | All | Team | Team |
| Create team job | All | Team | <Team> |
| Delete team job | All | Team | Self-created or <Team> |
| Configure team job | All | Team | Self-created or <Team> |
| Run team job | All | Team | Self-created or <Team> |
| Set team job public | All | Team | <Team> |