Pipeline triggers and upstream/downstream in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to trigger a downstream job named 'BuildApp'.

Jenkins

build job: '[1]'

Drag options to blanks, or click blank then click option'

ADeployApp

BBuildApp

CTestApp

DCleanApp

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong job name that does not exist.

Forgetting to put the job name in quotes.

The build job: 'BuildApp' command triggers the downstream job named 'BuildApp'.

2fill in blank

medium

Complete the code to trigger a job and wait for its completion.

Jenkins

build job: 'TestApp', wait: [1]

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

Cmaybe

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a boolean.

Setting wait to false when you want to wait.

Setting wait: true makes the pipeline wait for the triggered job to finish before continuing.

3fill in blank

hard

Fix the error in the trigger syntax to correctly trigger the downstream job.

Jenkins

[1] job: 'BuildApp'

Drag options to blanks, or click blank then click option'

Abuild

Bstart

Crun

Dexecute

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'trigger' instead of 'build'.

Using 'start' which is not a Jenkins pipeline step.

The correct Jenkins pipeline syntax to trigger a job is build, not trigger or others.

4fill in blank

hard

Fill both blanks to define a pipeline that triggers 'TestApp' after 'BuildApp' completes.

Jenkins

pipeline {
  stages {
    stage('Build') {
      steps {
        build job: '[1]'
      }
    }
    stage('Test') {
      steps {
        build job: '[2]'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

ABuildApp

BDeployApp

CTestApp

DCleanApp

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the job names in the stages.

Using job names that do not exist.

The first stage triggers 'BuildApp', and after it completes, the second stage triggers 'TestApp'.

5fill in blank

hard

Fill all three blanks to create a pipeline that triggers 'BuildApp', waits for it, then triggers 'TestApp' with parameters.

Jenkins

pipeline {
  stages {
    stage('Build') {
      steps {
        build job: '[1]', wait: [2]
      }
    }
    stage('Test') {
      steps {
        build job: '[3]', parameters: [string(name: 'ENV', value: 'prod')]
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

ABuildApp

Btrue

CTestApp

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Not waiting for the build job to finish.

Using wrong job names or missing parameters.

The pipeline triggers 'BuildApp' and waits for it to finish (wait: true), then triggers 'TestApp' with a parameter.

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