Conditional deployment logic in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline snippet?

Consider this Jenkins pipeline script snippet that decides deployment based on branch name:

pipeline {
  agent any
  stages {
    stage('Deploy') {
      when {
        expression { env.BRANCH_NAME == 'main' }
      }
      steps {
        echo 'Deploying to production!'
      }
    }
  }
}

If the pipeline runs on branch feature-xyz, what will be the output?

Jenkins

pipeline {
  agent any
  stages {
    stage('Deploy') {
      when {
        expression { env.BRANCH_NAME == 'main' }
      }
      steps {
        echo 'Deploying to production!'
      }
    }
  }
}

A The pipeline prints 'Deploying to production!'

B The pipeline runs the 'Deploy' stage but prints an empty line

C The pipeline fails with a syntax error

D The pipeline skips the 'Deploy' stage and prints nothing

💡 Hint

Think about the when condition and the branch name.

The when condition checks if BRANCH_NAME is 'main'. Since the branch is 'feature-xyz', the condition is false, so the 'Deploy' stage is skipped and nothing is printed.

❓ Configuration

intermediate

Which Jenkinsfile snippet deploys only on tags starting with 'v'?

You want to deploy your application only when a Git tag starts with the letter 'v' (e.g., 'v1.0'). Which when condition snippet achieves this?

A when { tag pattern: '^v.*', comparator: 'REGEXP' }

B when { branch 'v*' }

C when { expression { env.TAG_NAME.startsWith('v') } }

D when { tag 'v*' }

💡 Hint

Tags can be matched with regex patterns in Jenkins when conditions.

Option A uses the tag condition with a regex pattern to match tags starting with 'v'. Option A would fail if TAG_NAME is undefined. Options B and D are invalid syntax for tags.

🔀 Workflow

advanced

Identify the correct conditional deployment flow in a Jenkins pipeline

Given a Jenkins pipeline with stages for build, test, and deploy, you want to deploy only if tests pass and the branch is 'release'. Which snippet correctly implements this logic?

A

stage('Deploy') {
  when {
    expression { currentBuild.result == 'SUCCESS' && env.BRANCH_NAME == 'release' }
  }
  steps {
    echo 'Deploying release'
  }
}

B

stage('Deploy') {
  when {
    anyOf {
      expression { currentBuild.result == 'SUCCESS' }
      branch 'release'
    }
  }
  steps {
    echo 'Deploying release'
  }
}

C

stage('Deploy') {
  when {
    not {
      expression { currentBuild.result != 'SUCCESS' }
    }
    branch 'release'
  }
  steps {
    echo 'Deploying release'
  }
}

D

stage('Deploy') {
  when {
    allOf {
      expression { currentBuild.result == 'SUCCESS' }
      branch 'release'
    }
  }
  steps {
    echo 'Deploying release'
  }
}

💡 Hint

Use a single expression combining both conditions for clarity.

Option A correctly uses a single expression checking both that the build succeeded and the branch is 'release'. Option A uses allOf but currentBuild.result may not be set at that point. Option A uses anyOf which allows deployment if either condition is true, which is incorrect. Option A mixes not and branch incorrectly.

❓ Troubleshoot

advanced

Why does this Jenkins pipeline always skip the deploy stage?

Look at this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Deploy') {
      when {
        branch 'main'
      }
      steps {
        echo 'Deploying to production'
      }
    }
  }
}

Even when running on the 'main' branch, the 'Deploy' stage is skipped. What is the most likely cause?

Jenkins

pipeline {
  agent any
  stages {
    stage('Deploy') {
      when {
        branch 'main'
      }
      steps {
        echo 'Deploying to production'
      }
    }
  }
}

A The pipeline agent is not compatible with the <code>branch</code> condition

B The syntax for <code>branch</code> condition is incorrect; it needs to be <code>branch name: 'main'</code>

C The <code>branch</code> condition requires the environment variable <code>BRANCH_NAME</code> to be set, which is missing

D The <code>when</code> block must be inside <code>steps</code> to work

💡 Hint

Check if the pipeline environment has the branch name variable set.

The branch condition depends on the BRANCH_NAME environment variable, which Jenkins sets automatically for multibranch pipelines. If running a simple pipeline without this variable, the condition always fails, skipping the stage.

✅ Best Practice

expert

Which approach best ensures safe conditional deployment in Jenkins pipelines?

To avoid accidental deployments, you want to deploy only when all tests pass, the branch is 'main', and a manual approval is given. Which Jenkins pipeline snippet best implements this?

A

stage('Deploy') {
  when {
    allOf {
      expression { currentBuild.result == 'SUCCESS' }
      branch 'main'
      expression { input message: 'Approve deployment?' }
    }
  }
  steps {
    echo 'Deploying to production'
  }
}

B

stage('Deploy') {
  when {
    expression { currentBuild.result == 'SUCCESS' && env.BRANCH_NAME == 'main' }
  }
  steps {
    input 'Approve deployment?'
    echo 'Deploying to production'
  }
}

C

stage('Deploy') {
  steps {
    input 'Approve deployment?'
    when {
      expression { currentBuild.result == 'SUCCESS' && env.BRANCH_NAME == 'main' }
    }
    echo 'Deploying to production'
  }
}

D

stage('Deploy') {
  when {
    expression { currentBuild.result == 'SUCCESS' && env.BRANCH_NAME == 'main' }
  }
  steps {
    echo 'Deploying to production'
  }
  post {
    always {
      input 'Approve deployment?'
    }
  }
}

💡 Hint

Manual approval should be a step, not part of the when condition.

Option B correctly places the manual approval input step inside steps after the when condition. Option B incorrectly places when inside steps. Option B tries to use input inside when, which is invalid. Option B requests approval after deployment, which is unsafe.