Jenkins has support for matrix based security ( https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup) so you can configure it to allow certain users/groups to have access only to certain features/projects, but the way we have been using it has more been along the lines of where we have sysadmin related jobs on servers that only sysadmins have access to, then we have the normal cron tier that users/developers have read-only access to (cant create or execute jobs, but can view output), and then we have another tier where the developers can actually create/execute jobs. The tier that non-admins can create/execute jobs also has less access than our other environments, so a user wouldn't be able to create a job that ran as a user that has access to other systems for example.
Mike
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
