Difference between revisions of "Hudson-ci/features/Team Concept"

From Eclipsepedia

Jump to: navigation, search
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 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  
  
== Concept<br> ==
+
== Concept<br> ==
'''System admin '''<br> ===
+
  
Every Hudson instance will have at least one Sys Admin. Each Sys Admin will have Hudson wide authorization. Some of the main responsibilities are<br>
+
=== '''System admin '''<br> ===
  
*Responsible to set up team and adding a team admin<br>
+
Every Hudson instance will have at least one Sys Admin. Each Sys Admin will have Hudson wide authorization. Some of the main responsibilities are<br>
*Other higher level administration like installing plugin  
+
 
*<br>
+
*Set up team and adding a team admin<br>  
 +
*All&nbsp; higher level administrations like installing plugin, setting up security, and configuring the system<br>
  
=== '''Team Admin'''<br> ===
+
=== '''Team Admin'''<br> ===
  
Every team will have at least one team admin . Team admin has less power. Each Team Admin will have team wided authorization.&nbsp; Some of the main responsibilities are<br>
+
Every team will have at least one team admin . Team admin has less power. Each Team Admin will have team wided authorization.&nbsp; Some of the main responsibilities are<br>  
  
 
*Add and remove team members  
 
*Add and remove team members  
 
*<br>
 
*<br>
  
=== '''Team member '''<br> ===
+
=== '''Team member '''<br> ===
  
Each team will have one or more members.&nbsp; The authorizations are<br>
+
Each team will have one or more members.&nbsp; The authorizations are<br>  
  
 
*Can create and configure job if team admin admits  
 
*Can create and configure job if team admin admits  
Line 27: Line 27:
 
*Can run any team job and public job<br>
 
*Can run any team job and public job<br>
  
=== Authorization&nbsp; Schemes<br> ===
+
=== Authorization&nbsp; Schemes<br> ===
  
The three authorization schemes&nbsp; are<br>
+
The three authorization schemes&nbsp; are<br>  
  
 
#System Admin Authorization  
 
#System Admin Authorization  
Line 54: Line 54:
 
*Only certain team members can delete job build<br>
 
*Only certain team members can delete job build<br>
  
=== Job Visibility<br> ===
+
=== Job Visibility<br> ===
  
The visibility of a job can be set to<br>
+
The visibility of a job can be set to<br>  
  
'''public '''<br>
+
'''public '''<br>  
  
*Any one can view this job<br>
+
*Any one can view this job<br>  
 
*Only members can configure, run and delete the job<br>
 
*Only members can configure, run and delete the job<br>
  
'''Team private'''<br>
+
'''Team private'''<br>  
  
 
*Only visible to team members<br>
 
*Only visible to team members<br>
  
Particular team can only view their jobs and any public jobs.&nbsp; Anonymous users can view jobs only allowed to view as public <br>
+
Particular team can only view their jobs and any public jobs.&nbsp; Anonymous users can view jobs only allowed to view as public <br>  
  
 
&nbsp;
 
&nbsp;

Revision as of 21:49, 23 May 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

Contents

Concept

System admin

Every Hudson instance will have at least one Sys Admin. Each Sys Admin will have Hudson wide authorization. Some of the main responsibilities are

  • Set up team and adding a team admin
  • All  higher level administrations like installing plugin, setting up security, and configuring the system

Team Admin

Every team will have at least one team admin . Team admin has less power. Each Team Admin will have team wided authorization.  Some of the main responsibilities are

  • Add and remove team members

Team member

Each team will have one or more members.  The authorizations are

  • 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

Authorization  Schemes

The three authorization schemes  are

  1. System Admin Authorization
  2. Team Admin Authorization
  3. Team Member Authorization

Job scope

There are two scopes

Public Scope

  • Any one can view this job
  • Only Sys Admin can delete this job
  • Only Sys Admin can configure this job
  • Only Sys Admin can run this job

Team Scope

  • 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

Job Visibility

The visibility of a job can be set to

public

  • Any one can view this job
  • Only members can configure, run and delete the job

Team private

  • Only visible to team members

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
Create system admin Y - -
Create team admin Y Team -
Create team member Y Team -
See team job Y Team Team
Create team job Y Team <Team>
Delete team job Y Team Self-created or <Team>
Configure team job Y Team Self-created or <Team>
Run team job Y Team Self-created or <Team>
Set team job public Y Team <Team>

Legend:

Scope Means
Y All teams
- Not allowed
Team Only within the same team
<Team> Only within the same team if capability granted by system or team admin
Self-created Only if created by that team member

Additional Requirements

  • Multiple teams must be able to use same name for a job.
  • Jobs must be saved in team specific folders
  • Build History should show only the jobs accessible to the current user
  • The people dashboard should display only the team members of the current user
  • Build executor status must display jobs of the current user team
  • When switching between Team administration to/from standard or no administration data (jobs) must not be lost

Desirable Features (For Discussion)

  • It would be good if team configurations were preserved even when team feature is not active. Currently, toggling security or switching security realms or authorization methods does not preserve previous configuration data. However, the investment in team configuration is liable to be substantial and responsibility divided among multiple people; it could be very difficult to recover manually.