Pipeline triggers and upstream/downstream in Jenkins - Commands & Configuration

Introduction

Sometimes, one task needs to start only after another task finishes. Pipeline triggers help connect these tasks so they run in order automatically without manual work.

When you want a build to start automatically after a code test finishes successfully.

When you have a deployment task that should run only after the build task completes.

When you want to chain multiple jobs so they run one after another without manual intervention.

When you want to trigger a notification job after a deployment finishes.

When you want to split a big process into smaller jobs that run in sequence.

Config File - Jenkinsfile

Jenkinsfile

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building the project'
      }
    }
    stage('Test') {
      steps {
        echo 'Running tests'
      }
    }
  }
  post {
    success {
      build job: 'Deploy', wait: false
    }
  }
}

This Jenkinsfile defines a simple pipeline with two stages: Build and Test.

After the pipeline succeeds, it triggers another job named 'Deploy' without waiting for it to finish.

This shows how to trigger a downstream job automatically after the current pipeline completes successfully.

Commands

This command manually triggers the 'Deploy' job in Jenkins to test if it runs correctly.

Terminal

jenkins-jobs build Deploy

Expected Output

Started build of job 'Deploy' #1\nWaiting for build to complete...\nBuild #1 SUCCESS\nFinished: SUCCESS

This command starts the main pipeline job 'BuildAndTest' which will run Build and Test stages, then trigger 'Deploy' automatically on success.

Terminal

jenkins-jobs build BuildAndTest

Expected Output

Started build of job 'BuildAndTest' #1\n[Pipeline] Start of Pipeline\n[Pipeline] echo\nBuilding the project\n[Pipeline] echo\nRunning tests\n[Pipeline] build\nTriggering job: Deploy\n[Pipeline] End of Pipeline\nFinished: SUCCESS

This command checks the build history of the 'Deploy' job to confirm it was triggered by the upstream pipeline.

Terminal

jenkins-jobs list-builds Deploy

Expected Output

Builds for job 'Deploy':\n#1 SUCCESS - triggered by BuildAndTest #1

Key Concept

If you remember nothing else from this pattern, remember: downstream jobs can be triggered automatically after upstream jobs finish to create smooth, connected pipelines.

Common Mistakes

Not setting the downstream job name correctly in the trigger step.

The pipeline will fail to trigger the downstream job, breaking the chain.

Use the exact job name in the build step, for example: build job: 'Deploy', wait: false

Forgetting to handle job success or failure before triggering downstream jobs.

Downstream jobs may run even if the upstream job failed, causing wasted work or errors.

Use post conditions like 'post { success { ... } }' to trigger downstream jobs only on success.

Triggering downstream jobs synchronously without 'wait: false' when not needed.

This causes the upstream job to wait and possibly slow down the pipeline unnecessarily.

Add 'wait: false' to trigger downstream jobs asynchronously unless you need to wait for their result.

Summary

Use the 'build' step in Jenkins pipelines to trigger downstream jobs automatically.

Place triggers inside 'post' blocks to control when downstream jobs run based on success or failure.

Verify downstream jobs run by checking their build history after triggering the upstream pipeline.

Practice

1. What is the main purpose of using pipeline triggers in Jenkins?

easy

A. To delete old job logs automatically

B. To manually run jobs one by one

C. To stop all jobs from running

D. To automatically start a job when another job finishes

Solution

1. Step 1: Understand pipeline triggers

   Pipeline triggers are used to start one job automatically after another job finishes.

2. Step 2: Identify the purpose

   This automation helps connect jobs without manual intervention.

3. Final Answer:

   To automatically start a job when another job finishes -> Option D

4. Quick Check:

   Pipeline triggers = automatic job start [OK]

Hint: Triggers start jobs automatically after others finish [OK]

Common Mistakes:

• Thinking triggers run jobs manually
• Confusing triggers with log cleanup
• Believing triggers stop jobs

2. Which syntax correctly triggers a downstream job named Build-App after the current pipeline completes successfully?

easy

A. build job: 'Build-App', propagate: true, wait: true

B. trigger job: 'Build-App' onSuccess

C. start job 'Build-App' after success

D. run job 'Build-App' always

Solution

1. Step 1: Recall Jenkins pipeline syntax for triggering jobs

   The correct syntax uses the build step with parameters like job, propagate, and wait.

2. Step 2: Match the correct syntax

   build job: 'Build-App', propagate: true, wait: true matches the correct syntax exactly.

3. Final Answer:

   build job: 'Build-App', propagate: true, wait: true -> Option A

4. Quick Check:

   Correct build step syntax = build job: 'Build-App', propagate: true, wait: true [OK]

Hint: Use 'build job:' syntax to trigger downstream jobs [OK]

Common Mistakes:

• Using incorrect keywords like 'trigger' or 'start'
• Missing required parameters
• Wrong order or syntax errors

3. Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
    stage('Trigger Test') {
      steps {
        build job: 'Test-Job', propagate: true, wait: true
      }
    }
  }
}

What happens when the 'Build' stage completes successfully?

medium

A. 'Test-Job' runs in parallel without waiting

B. The 'Test-Job' pipeline starts and Jenkins waits for it to finish

C. The pipeline stops after 'Build' stage

D. An error occurs because 'build' is not a valid step

Solution

1. Step 1: Understand the 'build' step with 'wait: true'

   The 'build' step triggers another job and waits for it to complete before continuing.

2. Step 2: Analyze the pipeline flow

   After 'Build' stage, 'Test-Job' starts and Jenkins waits for it to finish before moving on.

3. Final Answer:

   The 'Test-Job' pipeline starts and Jenkins waits for it to finish -> Option B

4. Quick Check:

   'build' with wait=true means wait for downstream job [OK]

Hint: Wait true means wait for downstream job to finish [OK]

Common Mistakes:

• Assuming downstream runs in parallel without waiting
• Thinking pipeline stops early
• Believing 'build' is invalid step

4. You have this pipeline snippet:

build job: 'Deploy-App', propagate: false, wait: true

What issue might occur if 'Deploy-App' fails?

medium

A. Jenkins throws a syntax error

B. The current pipeline stops immediately on failure

C. The current pipeline continues despite failure in 'Deploy-App'

D. 'Deploy-App' runs twice

Solution

1. Step 1: Understand 'propagate: false'

   This setting means the failure of the downstream job does not fail the current pipeline.

2. Step 2: Analyze failure behavior

   If 'Deploy-App' fails, the current pipeline will continue running instead of stopping.

3. Final Answer:

   The current pipeline continues despite failure in 'Deploy-App' -> Option C

4. Quick Check:

   propagate false = ignore downstream failure [OK]

Hint: propagate false lets pipeline ignore downstream failures [OK]

Common Mistakes:

• Assuming pipeline stops on downstream failure
• Confusing propagate with wait
• Expecting syntax errors

5. You want to create a Jenkins pipeline where Job A triggers Job B only if Job A succeeds, and Job B triggers Job C regardless of its result. Which configuration correctly achieves this?

hard

A. In Job A pipeline: build job: 'Job-B', propagate: true, wait: trueIn Job B pipeline: build job: 'Job-C', propagate: false, wait: false

B. In Job A pipeline: build job: 'Job-B', propagate: false, wait: falseIn Job B pipeline: build job: 'Job-C', propagate: true, wait: true

C. In Job A pipeline: build job: 'Job-B', propagate: true, wait: falseIn Job B pipeline: build job: 'Job-C', propagate: true, wait: true

D. In Job A pipeline: build job: 'Job-B', propagate: false, wait: trueIn Job B pipeline: build job: 'Job-C', propagate: false, wait: true

Solution

1. Step 1: Ensure Job B triggers only on Job A success

   Using propagate: true in Job A means failure in Job B will fail Job A, so Job B runs only if Job A succeeds.

2. Step 2: Ensure Job C triggers regardless of Job B result

   Using propagate: false and wait: false in Job B triggers Job C without waiting and ignores Job C's result.

3. Final Answer:

   Option A matches these requirements -> Option A

4. Quick Check:

   propagate true for success-only triggers, false for unconditional [OK]

Hint: Use propagate true for success-only, false for unconditional triggers [OK]

Common Mistakes:

• Using propagate false when success-only is needed
• Confusing wait true/false effects
• Triggering downstream jobs incorrectly