Jenkins Advanced Series--14 configuration Jenkins user and Permissions __jenkins-ci build

Today we talk about the use of Jenkins proprietary user database configuration, and some commonly used permissions configuration. Configure user Registration  

In the Jenkins home page, click on the left side of the system management->configure Global security to enter the following interface:

As shown above, the option to manage users appears in system management after saving. The Login/Registration option also appears in the upper-right corner of the page.

Click to register:

Click the Sign Up button to indicate that you are now logged in. Configure user Rights

Click on the left side of the system management->configure Global Security

Select the security matrix or project matrix authorization policy in the authorization policy

Description: The configuration of the security matrix and the project matrix authorization policy is identical, and the only difference is that the project matrix authorization policy supports configuring the authorization policy again on the job's configuration page.

Add the user to the matrix, as shown in the following figure.

The various permissions are as follows (you can view Help on the configuration page by placing the mouse over that permission):

Overall (global)

Credentials (voucher)

Slave (node)

Job (Task)

View (views)

administer

Read

runscripts

uploadplugins

configureupdatecenter

Create

Update

View

Delete

managedomains

Configure

Delete

Create

Disconnect

Connect

build

create

Delete

Configure

Read

Discover

build

Workspace

Cancel

Create

Delete

Configure

Read

Administrator (max)

Read

Run the script

Upgrade Plugins

Configure Upgrade Center

Create

Update

View

Delete

Admin domain

Configuration

Delete

Create

Disconnect

Connection

Build

Create

Delete

Configuration

Read

redirect

Build

viewing workspaces

Cancel Build

Create

Delete

Configuration

Read

Some of the more specific permissions:

The maximum permission is the overall administer, which can do anything with that permission.

The most basic permission is overall read, the user must give permission to read, otherwise nothing can be seen.

Job discover permissions are a wonderful privilege, helping to say that discover is lower than the read level. If an anonymous user (without permission to access the job) directly accesses a job's URL, it is redirected to the landing page. (After testing, this permission should be discarded.) )

Credentials Managedomains This permission does not understand what to do, have understood everybody together exchanges ha.

PS: If a user is given a overall read, and the Read permission is not given to the job, then the user cannot access the job. Reason: No permissions.

Others are some of the basic competencies that everyone chooses according to their own needs.

Small tips:

Each user has 1-2 icons, the first is the reverse function (delete the currently selected permissions, select all other permissions), and the second is the delete feature (delete the user)

Configure project security in the job, as shown in the following figure:

Ext: http://www.cnblogs.com/zz0412/p/jenkins_jj_14.html Click on the Open link