Shipping the Approved Build is a practical Jenkins project for learners who know basic Pipeline navigation and want to deliver an existing build reliably. Work with Walk Weekender, a fictional event organizer whose visitor pack contains working pages, a route illustration, stops data and complete visitor notes.
Two Guided Labs take you from a successful build with no retained download to a complete archived pack, then to a separate delivery job that retrieves the confirmed existing run. One independent Challenge changes the activity and source relationship, including another activity with similar edition codes. Each unit starts in a fresh prepared environment.
What You Will Learn
After completing this course, you will be able to:
- retain a complete build artifact before Jenkins clears its workspace;
- download and use a visitor pack with working local pages, images, CSV and notes;
- compare activity, edition and build result to identify a confirmed existing source run;
- replace a moving source selection with an explicit job and build number using Copy Artifact;
- trace the original archive through Jenkins fingerprints to a separate delivery build;
- deliver the original package while preserving another activity and both jobs' cleanup.
Who This Course Is For
This course is for beginning Jenkins users, developers and DevOps learners who want a small, complete artifact-delivery task.
Prerequisites: Basic Jenkins navigation, recognition of a short Declarative Pipeline, and basic file handling, including extracting a ZIP. Complete the Pipeline introduction in Jenkins for Beginners first if these are new. Archiving, workspace cleanup, fingerprints and explicit source selection are explained before use. No Java or website programming is required.
Learning environment: Each activity provides Jenkins and the Pack Desk browser entries, prepared event files and a working builder. Copy Artifact is prepared where it is needed. No cloud account, public Git service or local software installation is required. Downloaded archives are saved on your own computer. The event websites, interface labels and program output remain English; learning documents are available in nine languages.
Frequently Asked Questions
Will I build the website or install Jenkins plugins?
No. The visitor files, builder and required plugin are provided. You change a short Pipeline, choose source parameters and inspect the actual files and build trace.
Why not always copy the latest successful build?
A newer successful run can contain an unconfirmed draft. This project lets you compare real archived editions and deliver the existing run that matches the request, even after its workspace has been cleared.
Does a fingerprint prove that a release was approved?
No. Jenkins fingerprints trace file identity and usage between builds. The business request identifies the confirmed edition; the course does not implement an approval workflow or publisher signatures.
What is the delivery target?
A small local training receiver serves the delivered visitor files through Pack Desk and rejects packages that do not match its fixed request. This is a focused Jenkins exercise, not a production artifact registry. The independent Challenge uses the same taught mechanisms and includes a complete separate solution.
Cover mascot adapted with AI from artwork by the Jenkins project, under CC BY-SA 3.0.
