Jenkins User Rights Management

Reference article:
Jenkins Rights Management plug-in

role-based Authorization Strategy setting security policy

Path: System Management-configure Global security-authorization policy, select role-based Strategy:

Manager and Assign roles option appears in system administration after save

User Rights setting options

Path: System Management-manager and Assign Roles, with three menus

-Manage Roles
-Assign Roles
-Role Strategy Macros Manage Roles

The permission of this class is actually a group or a kind of people's permission, in the original permission classification of a large class, the scattered permissions are categorized, respectively, divided into
-Global roles: Universal Role permissions
-Project roles: Item role permissions
-Slave Roles: node role permissions Assign roles

After manage roles to classify permissions, we can assign different permissions to different people here. Role Strategy Macros

Ignore user Rights settings

Before setting permissions, let's take a look at what permissions a user without any configuration has:

Directly denied access, according to the prompt is because there is no overall/read permissions, we give him to open Overall/read permissions. Add Overall/read Permissions

First create a role name with the global view permission, and I'll call the Overall_read character for the sake of the name.

And then give anonymous to the Overall_read permissions, even the user can see the non-login, naturally other users can also see.

At this point, we can see that the page that was denied access before landing becomes the following page:

Then I took a few clicks and found that the job could not be created, giving job/create permission to create the job

Create a global role:job_create, and then create a project Role:inf that matches all items beginning with the INF

The anonymous user is then given the job_create role and INF project role.

This time Qianhui the user has permission to create any job, but only the job that begins with the INF is visible and manipulated.
If you create a job that does not start with an INF, it will report a 404 error, but the job has actually been created, but it is not visible.
Project Administrator Permissions

For a normal user, the above permissions are enough, if you do not want to be disturbed because of other permissions, then to each project to establish an administrator rights, to give a person, the project after the problem to find this person on the line, lazy good way.