Conditional deployment logic in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run deployment only if the branch is 'main'.

Jenkins

if (env.BRANCH_NAME == '[1]') {
  echo 'Deploying to production...'
}

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

Adevelop

Bfeature

Cmain

Dtest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'develop' or other branch names instead of 'main'.

Forgetting to compare the branch name as a string.

The deployment should happen only on the 'main' branch, so the condition must check for 'main'.

2fill in blank

medium

Complete the code to skip deployment if the build is triggered by a pull request.

Jenkins

if (env.CHANGE_ID == [1]) {
  echo 'Deploying...'
} else {
  echo 'Skipping deployment for pull request.'
}

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

Atrue

Bnull

C0

D''

Attempts:

3 left

💡 Hint

Common Mistakes

Using empty string '' instead of null.

Using 0 or true which are not valid for this check.

When the build is not a pull request, CHANGE_ID is null. So to skip deployment on PRs, check if CHANGE_ID is not null.

3fill in blank

hard

Fix the error in the condition to deploy only on 'release' branch and not on pull requests.

Jenkins

if (env.BRANCH_NAME == '[1]' && env.CHANGE_ID == null) {
  echo 'Deploying release build...'
}

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

Afeature

Bmain

Cdevelop

Drelease

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'main' or 'develop' instead of 'release'.

Not checking for pull request correctly.

The deployment should happen only on the 'release' branch and when CHANGE_ID is null (not a pull request).

4fill in blank

hard

Fill both blanks to deploy only if the branch is 'main' and the build is not a pull request.

Jenkins

if (env.BRANCH_NAME == '[1]' && env.CHANGE_ID == [2]) {
  echo 'Deploying to production...'
}

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

Amain

Bnull

Cdevelop

D''

Attempts:

3 left

💡 Hint

Common Mistakes

Using empty string '' instead of null for CHANGE_ID.

Using wrong branch name.

Deployment happens only on 'main' branch and when CHANGE_ID is null (not a pull request).

5fill in blank

hard

Fill all three blanks to deploy only if the branch is 'develop', the build is not a pull request, and the environment is 'staging'.

Jenkins

if (env.BRANCH_NAME == '[1]' && env.CHANGE_ID == [2] && env.ENVIRONMENT == '[3]') {
  echo 'Deploying to staging environment...'
}

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

Adevelop

Bnull

Cstaging

Dproduction

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'production' instead of 'staging' for environment.

Using empty string '' instead of null for CHANGE_ID.

Using wrong branch name.

The deployment condition requires branch 'develop', no pull request (CHANGE_ID null), and environment 'staging'.

Practice

1. What is the main purpose of using a when block in a Jenkins pipeline?

easy

A. To define environment variables for the pipeline

B. To run a stage only if certain conditions are met

C. To specify the agent where the pipeline runs

D. To declare pipeline parameters

Solution

1. Step 1: Understand the role of when in Jenkins

   The when block controls whether a stage runs based on conditions.

2. Step 2: Compare options with when usage

   Only To run a stage only if certain conditions are met describes conditional execution, which matches when functionality.

3. Final Answer:

   To run a stage only if certain conditions are met -> Option B

4. Quick Check:

   when controls stage execution = A [OK]

Hint: Remember: when means "only if" for stages [OK]

Common Mistakes:

• Confusing when with environment setup
• Thinking when sets agents
• Assuming when declares parameters

2. Which of the following is the correct syntax to run a stage only on the 'main' branch in a declarative Jenkins pipeline?

easy

A. when { branch is 'main' }

B. when { branch == 'main' }

C. when { branch 'main' }

D. when { branch equals 'main' }

Solution

1. Step 1: Recall correct when syntax for branch condition

   The correct syntax uses branch 'main' inside when block.

2. Step 2: Check each option's syntax

   Only when { branch 'main' } matches Jenkins declarative syntax; others use invalid expressions.

3. Final Answer:

   when { branch 'main' } -> Option C

4. Quick Check:

   Correct branch syntax = C [OK]

Hint: Use branch 'name' exactly inside when [OK]

Common Mistakes:

• Using comparison operators inside when
• Writing invalid expressions like 'branch =='
• Confusing Groovy syntax with declarative syntax

3. Given this Jenkins pipeline snippet, what will happen if the branch is 'develop'?

stage('Deploy') {
  when {
    branch 'main'
  }
  steps {
    echo 'Deploying to production'
  }
}

medium

A. The stage will be skipped and nothing prints

B. The stage will run and print 'Deploying to production'

C. The pipeline will fail with a syntax error

D. The stage will run but print nothing

Solution

1. Step 1: Analyze the when condition

   The stage runs only if branch is 'main'. Here branch is 'develop', so condition fails.

2. Step 2: Determine stage behavior on condition failure

   When when condition fails, the stage is skipped and no steps run.

3. Final Answer:

   The stage will be skipped and nothing prints -> Option A

4. Quick Check:

   Branch mismatch skips stage = A [OK]

Hint: If branch doesn't match when, stage skips silently [OK]

Common Mistakes:

• Assuming stage runs anyway
• Expecting error on branch mismatch
• Thinking stage runs but prints nothing

4. Identify the error in this Jenkins pipeline snippet that tries to deploy only if environment variable DEPLOY is 'true':

stage('Deploy') {
  when {
    environment DEPLOY == 'true'
  }
  steps {
    echo 'Deploying application'
  }
}

medium

A. The stage name cannot be 'Deploy'

B. The when block must be inside steps

C. The echo command is not allowed in steps

D. The environment condition is invalid syntax

Solution

1. Step 1: Check when syntax for environment variable

   The correct syntax uses environment name: 'DEPLOY', value: 'true' or expression blocks, not direct comparison.

2. Step 2: Identify invalid usage

   Using environment DEPLOY == 'true' is invalid and causes syntax error.

3. Final Answer:

   The environment condition is invalid syntax -> Option D

4. Quick Check:

   Invalid environment condition syntax = D [OK]

Hint: Use correct when { environment name: 'VAR', value: 'val' } syntax [OK]

Common Mistakes:

• Writing direct comparisons inside when
• Placing when inside steps
• Misusing stage names

5. You want to deploy only if the branch is 'release' and the environment variable DEPLOY is 'yes'. Which when block correctly implements this in a declarative Jenkins pipeline?

hard

A. when { allOf { branch 'release'; environment name: 'DEPLOY', value: 'yes' } }

B. when { branch 'release' && environment DEPLOY == 'yes' }

C. when { branch 'release' environment DEPLOY == 'yes' }

D. when { anyOf { branch 'release'; environment name: 'DEPLOY', value: 'yes' } }

Solution

1. Step 1: Understand combining conditions in when

   Use allOf to require both conditions true simultaneously.

2. Step 2: Check syntax for branch and environment conditions

   when { allOf { branch 'release'; environment name: 'DEPLOY', value: 'yes' } } correctly uses allOf with branch 'release' and environment name: 'DEPLOY', value: 'yes'.

3. Step 3: Identify errors in other options

   Options A and C use invalid syntax; D uses anyOf which means either condition, not both.

4. Final Answer:

   when { allOf { branch 'release'; environment name: 'DEPLOY', value: 'yes' } } -> Option A

5. Quick Check:

   Use allOf for AND conditions = B [OK]

Hint: Use allOf to combine multiple when conditions [OK]

Common Mistakes:

• Using anyOf instead of allOf
• Writing invalid combined expressions
• Misusing environment condition syntax