08 · Continuous deliveryLab 45 / 59
Challengejenkins
Jenkins Pipeline: Build, Scan and Push an Image — Challenge
Take a commit to a scanned, tagged image in a registry, with a gate that blocks rather than reports.
- Time
- 27 min
- Level
- Intermediate
- Objectives
- 4 objectives
- Cost
- Free
Where this fits in the platform
Already built
This lab adds
- A commit that becomes a tagged image in the registry
Before you start
You will need
- Docker
- Jenkins with the Docker Pipeline plugin
- A registry account
You do not need these already — the lab environment below provides them.
You will be able to
- Build a container image from a pipeline without leaking credentials
- Fail a build on a vulnerability rather than logging one
- Tag images so a deployment can be traced to a commit
The goal#
Achieve the same outcome as Jenkins Pipeline: Build, Scan and Push an Image, from an empty starting point, without the steps.
The pipeline builds an image and pushes it as latest. Nobody can say which commit is in production, the scan runs after the push, and the registry password is an environment variable in the job configuration.
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#
- A push produces an image tagged with the short commit SHA in the registry.
- A HIGH or CRITICAL vulnerability fails the build — proven with a deliberately old base image.
- No credential appears in the build log.
- The
latesttag is not what gets deployed, and you can say why.
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 45 of 59 on the project path