Working with Jenkins Permissions

Get Started
30 minutes
  • 3 Learning Objectives

About this Hands-on Lab

In this hands-on lab, we will set up a working group that has a supervisor and two users. The supervisor account will be able to see the users’ resources, but the users will not be able to see one another’s resources. This will demonstrate an understanding of how permissions are applied in Jenkins.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Configure Global Security, Log in as the Administrator, and Create the Users and Folders
  1. Log in to the server using the provided credentials.
  2. Configure global security to utilize the Project-based Matrix Authorization Strategy.
  3. Create the three users as well as the frontend and backend folders.
Set the Permissions on the Folders per the Provided Instructions
  • Tom should only be able to see his folder and the jobs in that folder. He should not be able to see Lisa‘s folder or the jobs in that folder.
  • Lisa should not be able to see Tom‘s folder or the jobs in that folder. She should only be able to see her folder and the jobs in her folder.
  • Diane should be able to see both Lisa‘s and Tom‘s folders and jobs but should not be able to run those jobs.
Log in as Each of the Users and Verify Permissions Are Working Correctly
  1. Log in as Tom, and ensure he is only able to see the frontend folder.
  2. Create a test job in the frontend folder, and ensure it can run.
  3. Log in as Lisa, and ensure she is only able to see the backend folder.
  4. Create a test job in the backend folder, and ensure it can run.
  5. Log in as Diane, and that she can see both folders and the job status but is not able to run the jobs in those folders.

Additional Resources

In your company, there is a new group that will be working on frontend development of a project. Diane is the supervisor of this project, and she has two developers working for her. Tom needs to have a folder named frontend in which he places his builds. A test build should be created as Tom to ensure he is able to build in this folder. Lisa is the backend developer and needs a folder named backend. She should be able to create and run jobs in this folder. The folders should have the following rules:

  • Tom should not be able to see Lisa's folder or the jobs in that folder.
  • Lisa should not be able to see Tom's folder or the jobs in that folder.
  • Diane should be able to see both Lisa's and Tom's folders and jobs but should not be able to run those jobs.

The instance you have been provided has the following login credentials:

  • Username: student
  • Password: OmgPassword!
What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Get Started
Who’s going to be learning?

How many seats do you need?

  • $499 USD per seat per year
  • Billed Annually
  • Renews in 12 months

Ready to accelerate learning?

For over 25 licenses, a member of our sales team will walk you through a custom tailored solution for your business.


$2,495.00

Checkout
Sign In
Welcome Back!
Thanks for reaching out!

You’ll hear from us shortly. In the meantime, why not check out what our customers have to say about ACG?