Pipeline triggers and upstream/downstream in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Upstream and Downstream Jobs

In Jenkins, if Job A triggers Job B after it finishes successfully, which statement is true?

A Job A is the upstream job of Job B.

B Job B is the upstream job of Job A.

C Job A is the downstream job of Job B.

D Job A and Job B are unrelated in terms of triggers.

💡 Hint

Think about the direction of the trigger: who starts first and who follows.

In Jenkins, the job that triggers another is called the upstream job, and the job that is triggered is the downstream job. Since Job A triggers Job B, Job A is upstream and Job B is downstream.

💻 Command Output

intermediate

Output of a Jenkins Pipeline Trigger Script

What will be the output of this Jenkins pipeline snippet when Job A triggers Job B?

Jenkins

pipeline {
  agent any
  stages {
    stage('Trigger') {
      steps {
        build job: 'JobB', wait: true
        echo 'Job B completed'
      }
    }
  }
}

A Syntax error due to missing parameters

B Job B completed (immediately, without waiting)

C Job B completed (after Job B finishes)

D Job B is triggered but pipeline fails

💡 Hint

Check the meaning of wait: true in the build step.

The build step with wait: true waits for Job B to finish before continuing. So the echo runs after Job B completes.

❓ Configuration

advanced

Configuring Upstream Job to Trigger Multiple Downstream Jobs

Which Jenkins pipeline snippet correctly triggers two downstream jobs JobB and JobC in parallel and waits for both to finish?

Jenkins

pipeline {
  agent any
  stages {
    stage('Trigger') {
      steps {
        parallel {
          JobB: { build job: 'JobB', wait: true },
          JobC: { build job: 'JobC', wait: true }
        }
      }
    }
  }
}

A

parallel {
  JobB: { build job: 'JobB' },
  JobC: { build job: 'JobC' }
}

B

parallel {
  JobB: { build job: 'JobB', wait: true },
  JobC: { build job: 'JobC', wait: true }
}

C

stage('Trigger') {
  steps {
    build job: 'JobB'
    build job: 'JobC'
  }
}

D

stage('Trigger') {
  steps {
    build job: 'JobB', wait: false
    build job: 'JobC', wait: false
  }
}

💡 Hint

Remember that parallel runs branches at the same time and wait: true waits for each job to finish.

Option B uses parallel with wait: true for both jobs, so both run simultaneously and the pipeline waits for both to finish before continuing.

❓ Troubleshoot

advanced

Troubleshooting a Downstream Job Not Triggering

You have configured Job A to trigger Job B using the build step in a pipeline, but Job B never starts. What is the most likely cause?

A Job B is disabled or does not exist.

B Job A has no agent defined.

C The <code>build</code> step is missing <code>wait: true</code>.

D Job B is already running and cannot be triggered again.

💡 Hint

Check if the downstream job is available and enabled.

If Job B is disabled or does not exist, Jenkins cannot trigger it. Missing wait: true does not prevent triggering. Job B can be triggered multiple times unless restricted.

✅ Best Practice

expert

Best Practice for Triggering Upstream Job After Downstream Completion

You want Job A to start only after Job B completes successfully, but Job B is not triggered by Job A. Which Jenkins feature best supports this?

A Configure Job A to run on a timer and check Job B's logs.

B Use a polling trigger in Job A to check Job B's status.

C Use the <code>build</code> step in Job A to trigger Job B with <code>wait: true</code>.

D Configure Job B to trigger Job A as a downstream job on success.

💡 Hint

Think about how to start a job after another finishes when the first job is not triggered by the second.

Configuring Job B to trigger Job A on success ensures Job A runs only after Job B completes. Polling or timers are less efficient and more error-prone.