08 · Continuous deliveryLab 44 / 59
Challengejenkins
Jenkins Fundamentals & Role-Based Access — Challenge
Run Jenkins in a container, build a job from a webhook, and stop every authenticated user being an administrator.
- Time
- 25 min
- Level
- Beginner
- Objectives
- 4 objectives
- Cost
- Free
Where this fits in the platform
Already built
This lab adds
- A pipeline defined as code rather than clicked in a UI
Which lets you
Before you start
You will need
- Docker
- Docker Compose
You do not need these already — the lab environment below provides them.
You will be able to
- Run Jenkins reproducibly with persistent state
- Trigger a build from a push rather than a button
- Grant permissions by role rather than to everyone
The goal#
Achieve the same outcome as Jenkins Fundamentals & Role-Based Access, from an empty starting point, without the steps.
Jenkins out of the box gives every authenticated user broad permissions, and its state lives inside a container that will be replaced.
Neither is acceptable, and both are fixed before writing a single pipeline.
Hands-on environment
Run this lab in a real terminal, free and in your browser. The environment is temporary and yours alone — break it as much as you like.
Start the challengeOpens in Killercoda, in a new tab — keep this page open for the steps.
This is the guided lab's environment — the same machine, with its walkthrough on the left. Work from the task above and leave those steps alone until you are done, or you are reading the answers.
Run it on your own machine
Run this lab on your own machine. One command starts the environment, with everything the lab needs already installed:
You will need:
- docker
git clone https://github.com/EgyKode/EgyKode-lab.git
cd EgyKode-lab
./egykode start cicd
./egykode shellYou need Docker and Git installed. Everything else runs inside the environment. The first start downloads it and takes a few minutes; later starts are seconds.
Not sure what you already have? Run: npm run doctor — it checks and changes nothing.
Anything you tick here is your own record. EgyKode cannot see inside that terminal, so the success criteria stay self-assessed even when the environment checks your work for you.
What must be true when you are done
Step 1 of 3
What must be true when you are done#
- Jenkins is running with its home directory on a named volume, surviving a container restart.
- A job builds automatically when a commit is pushed.
- Two users exist: one administrator, one read-only, verified by logging in as each.
- The read-only user cannot start a build — demonstrated, not assumed.
Rules#
- Do not open the guided lab until you are finished, or until the same problem has held you up for 20 minutes.
- Documentation is allowed and encouraged.
- Verify every criterion with a command whose output you can read.
If you get stuck#
- What did you expect, exactly?
- What happened instead — the error text, not a paraphrase?
- Which layer is that error from?
- What is the smallest command that proves the layer below is fine?
You are done when
0 of 4
The concept behind it
Next up
Lab 44 of 59 on the project path