Prevent Stale Releases

Use ordered milestones to stop older runs overtaking newer releases.

A advanced Jenkins challenge worth 20 points. Solve it hands-on in a real Jenkins environment in your browser - no local setup, no fake shells.

The Challenge

Scenario: Slow older builds can cross release boundaries after newer builds and publish stale output.

Requirements:

• Add milestone 10 before release preparation
• Add milestone 20 after release preparation
• Keep concurrent runs enabled so a newer build can supersede an older one
• Run the build through both release boundaries