Deployment pipelines (dev, staging, prod) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Pipeline Stage Execution Order

Given this Jenkins pipeline snippet, what will be the order of stage execution?

pipeline {
  agent any
  stages {
    stage('Dev') {
      steps { echo 'Deploying to Dev' }
    }
    stage('Staging') {
      steps { echo 'Deploying to Staging' }
    }
    stage('Prod') {
      steps { echo 'Deploying to Prod' }
    }
  }
}

Jenkins

pipeline {
  agent any
  stages {
    stage('Dev') {
      steps { echo 'Deploying to Dev' }
    }
    stage('Staging') {
      steps { echo 'Deploying to Staging' }
    }
    stage('Prod') {
      steps { echo 'Deploying to Prod' }
    }
  }
}

A 1,3,2

B 3,2,1

C 2,1,3

D 1,2,3

💡 Hint

Stages run in the order they are defined in the Jenkinsfile.

Jenkins executes pipeline stages sequentially in the order they appear in the Jenkinsfile unless parallel is used.

❓ Configuration

intermediate

Correct Jenkinsfile Syntax for Conditional Deployment

Which Jenkinsfile snippet correctly deploys to Prod only if the branch is main?

A

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

B

stage('Prod') {
  when {
    branch == 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

C

stage('Prod') {
  when {
    branch = 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

D

stage('Prod') {
  when {
    branch != 'main'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

💡 Hint

Check the correct syntax for the when condition in Jenkins declarative pipeline.

The when { branch 'main' } syntax is the correct way to conditionally run a stage only on the main branch.

❓ Troubleshoot

advanced

Jenkins Pipeline Fails on Staging Deployment

A Jenkins pipeline deploys successfully to Dev but fails at the Staging stage with this error:

ERROR: script returned exit code 1

Which option is the most likely cause?

A The Staging deployment script has a command that returns a non-zero exit code.

B The Jenkinsfile syntax is invalid causing the pipeline to fail before Staging.

C The Dev stage is skipped, so Staging cannot run.

D The Prod stage is running before Staging causing a conflict.

💡 Hint

Non-zero exit codes usually indicate a failure in shell commands.

The error means a command in the Staging deployment script failed and returned exit code 1, causing the pipeline to stop.

🔀 Workflow

advanced

Jenkins Pipeline with Manual Approval Before Production

Which Jenkins pipeline snippet correctly adds a manual approval step before deploying to Production?

A

stage('Prod') {
  steps {
    input 'Approve Production Deployment?'
    echo 'Deploying to Prod'
  }
}

B

stage('Prod') {
  steps {
    echo 'Deploying to Prod'
    input 'Approve Production Deployment?'
  }
}

C

stage('Prod') {
  steps {
    timeout(time: 1, unit: 'MINUTES') {
      input 'Approve Production Deployment?'
    }
    echo 'Deploying to Prod'
  }
}

D

stage('Prod') {
  when {
    input 'Approve Production Deployment?'
  }
  steps {
    echo 'Deploying to Prod'
  }
}

💡 Hint

Manual approval uses input step, and timeout is good practice to avoid hanging.

Option C correctly uses input with a timeout to wait for manual approval before deploying.

✅ Best Practice

expert

Best Practice for Managing Secrets in Jenkins Pipelines

What is the best practice for handling sensitive credentials like API keys in Jenkins pipelines for deployment to multiple environments?

A Store secrets directly in the Jenkinsfile as plain text variables.

B Use Jenkins Credentials Plugin to securely store and inject secrets during pipeline execution.

C Commit secrets encrypted in the source code repository and decrypt them in the pipeline.

D Ask users to input secrets manually every time the pipeline runs.

💡 Hint

Think about security and automation in pipelines.

Using Jenkins Credentials Plugin is the recommended way to securely manage secrets without exposing them in code or logs.