Building a Photo Pack Across Agents

Process photos on one Jenkins agent, transfer their output to another, and retain a complete offline gallery while preserving the originals.

ProjectJenkinsDevOps

Introduction

Building a Photo Pack Across Agents is a Jenkins project course for learners who know basic job navigation and can recognize a short Declarative Pipeline. Help the fictional Fieldlight Studio turn three large photographs into small previews, a contact sheet and a complete downloadable gallery while keeping the originals safe.

Two Guided Labs introduce the work in independent environments: first choose the image-capable agent and respond to a smaller preview request, then transfer its output to a separate packaging agent. One Challenge applies the same mechanisms to a different workshop collection and image-size requirement. Each unit starts with its own prepared state; only your knowledge carries over.

What You Will Learn

  • select an agent by its actual capability labels and interpret a missing-tool failure;
  • change the supplied image tool's width option and retain both preview versions without changing the originals;
  • explain why two allocated agent workspaces do not automatically share generated files;
  • transfer only the small prepared output with matching native stash and unstash steps inside one Pipeline run;
  • retain the complete photo ZIP with Jenkins artifacts and fingerprints, keep stage cleanup, and use the extracted gallery and attachments offline.

Who This Course Is For

This course suits Jenkins beginners and developers starting to distribute build work across agents. You should already be comfortable opening a job, reading a build console and recognizing the structure of a short Declarative Pipeline. Agents, labels, workspaces and the required transfer steps are explained before use. Java programming, image-processing implementation, Docker administration and agent installation are not prerequisites.

Learning environment: LabEx provides the Photo Desk and Jenkins browser Interfaces, connected agents, original study photographs and complete processing/packaging tools. You edit short Pipeline scripts through Jenkins. The two agents have separate container filesystems on one training VM and share its kernel; this is a controlled local workflow, not a cloud fleet or a production isolation guarantee. The websites, UI labels and runtime output remain in English.

Frequently Asked Questions

Do I need to install Jenkins or connect agents?

No. Jenkins, its required plugins, both agent connections and the role-specific tools are ready. You focus on scheduling, file handoff and a usable delivery.

Do I need to write image-processing code?

No. Complete tools are provided. You choose the taught width option and Pipeline placement, then inspect the actual photographs, captions and files they produce. The photographs are original AI-generated study materials and depict no real client or event.

How is a stash different from an artifact?

A stash temporarily moves a selected small file set within the same Pipeline run. Native artifact archiving retains output with its build for later download. The course uses both and keeps workspace cleanup so the difference is visible.

What makes the Challenge independent?

It changes the collection and requested dimensions, with a clear final delivery and preservation requirements. It reuses taught tools and mechanisms in a separately prepared environment; it does not depend on earlier VM files. Your result is a complete local gallery, not a report or a copied success message.

Cover artwork adapts the Jenkins mascot, originally created by Frontside with Charles Lowell championing the design, under CC BY-SA 3.0 Unported; see the official Jenkins artwork. The course composition is an AI-assisted derivative for LabEx. This does not imply Jenkins endorsement and is separate from the original study-photo provenance.

Teacher

labby
Labby
Labby is the LabEx teacher.