Milestone step for concurrency in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of the Milestone Step in Jenkins Pipelines

What is the main purpose of using the milestone step in a Jenkins pipeline?

A To pause the pipeline execution until a manual approval is given.

B To mark a point in the pipeline that prevents older builds from running past it if a newer build has reached the same milestone.

C To trigger parallel execution of multiple stages simultaneously.

D To archive build artifacts at a specific stage.

💡 Hint

Think about how Jenkins manages concurrent builds and avoids outdated work continuing.

The milestone step helps Jenkins pipelines handle concurrency by ensuring that if a newer build reaches a milestone, older builds that haven't reached it yet will be stopped. This prevents outdated builds from wasting resources.

💻 Command Output

intermediate

Output of Pipeline with Milestone Step

Given the following Jenkins pipeline snippet, what will be the output if build #2 reaches the milestone before build #1?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        milestone 1
        echo "Build stage running"
      }
    }
    stage('Test') {
      steps {
        milestone 2
        echo "Test stage running"
      }
    }
  }
}

A Build #2 will stop at milestone 1 and not run 'Build stage running'.

B Both builds run all stages fully without interruption.

C Build #1 and Build #2 will both stop at milestone 1.

D Build #1 will stop at milestone 2 and not run 'Test stage running', while Build #2 runs both stages fully.

💡 Hint

Remember that milestone stops older builds from passing milestones reached by newer builds.

When Build #2 reaches milestone 2 first, Build #1 is considered older and will be stopped before running the 'Test' stage, so it won't print 'Test stage running'. Build #2 runs fully.

🔀 Workflow

advanced

Using Milestone to Control Parallel Branches

In a Jenkins pipeline with parallel branches, how can the milestone step be used to ensure that only the latest build's parallel branches proceed beyond a certain point?

A Use <code>milestone</code> inside a single sequential stage, not in parallel branches.

B Use <code>milestone</code> only after all parallel branches complete to stop older builds.

C Place a <code>milestone</code> step at the start of each parallel branch to stop older builds from continuing in any branch once a newer build passes the milestone.

D Milestone steps cannot be used with parallel branches.

💡 Hint

Think about how to stop outdated work in each parallel path individually.

By placing a milestone step at the start of each parallel branch, Jenkins can stop older builds from continuing in any branch once a newer build has passed that milestone, preventing wasted work in parallel branches.

❓ Troubleshoot

advanced

Troubleshooting Unexpected Pipeline Stops with Milestone

A Jenkins pipeline with milestones unexpectedly stops an older build early. What is the most likely cause?

A A newer build has already passed the same milestone, causing the older build to be aborted at that point.

B The pipeline script has a syntax error causing premature termination.

C The Jenkins agent lost connection during the build.

D The milestone step was placed after all stages, so it never triggered.

💡 Hint

Consider how milestones affect concurrency and build ordering.

The milestone step aborts older builds that have not reached the milestone if a newer build has already passed it. This is the expected behavior to avoid running outdated builds.

✅ Best Practice

expert

Best Practice for Using Milestone Steps in Complex Pipelines

What is the best practice when placing milestone steps in a complex Jenkins pipeline to manage concurrency effectively?

A Place milestone steps at key points before resource-intensive or long-running stages to prevent older builds from wasting resources.

B Avoid using milestone steps in complex pipelines as they cause unpredictable behavior.

C Place milestone steps only at the very end of the pipeline to ensure all builds complete fully.

D Use milestone steps only in freestyle jobs, not in pipelines.

💡 Hint

Think about saving time and resources by stopping outdated builds early.

Placing milestone steps before expensive or long stages helps stop older builds early, saving resources and reducing queue times, which is a best practice in complex pipelines.