Build steps execution in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline step?

Consider this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building project...'
      }
    }
  }
}

What will Jenkins print in the console log during the Build stage?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building project...'
      }
    }
  }
}

A Building project...

B Build stage started

C Error: echo command not found

D No output

💡 Hint

The echo step prints the given message to the console log.

The echo step in Jenkins pipeline prints the specified string to the console output during the build.

🔀 Workflow

intermediate

Order of execution in Jenkins pipeline stages

Given this Jenkins pipeline:

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        echo 'Testing...'
      }
    }
    stage('Deploy') {
      steps {
        echo 'Deploying...'
      }
    }
  }
}

What is the correct order Jenkins executes these stages?

A Both stages run in parallel

B 1,2

C Stages run randomly

D 2,1

💡 Hint

Stages in Jenkins pipeline run sequentially by default.

Jenkins executes stages in the order they are defined unless parallel is specified.

❓ Troubleshoot

advanced

Why does this Jenkins pipeline fail to execute the shell command?

Look at this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'echo Building project'
      }
    }
  }
}

When running on a Windows agent, what error is most likely to occur?

A echo Building project

B Build completed successfully

C sh: command not found

D Syntax error in pipeline script

💡 Hint

The 'sh' step runs shell commands, which may not be available on Windows agents.

The 'sh' step requires a Unix shell environment. On Windows agents without such environment, it fails with 'sh: command not found'.

✅ Best Practice

advanced

Which Jenkins pipeline step ensures a build step runs only if the previous step succeeded?

In Jenkins declarative pipeline, which step or directive ensures that a build step runs only if the previous steps in the stage succeeded?

A use 'post' block with 'failure' condition

B use 'always' block

C use 'parallel' block

D steps inside a stage run sequentially and stop on failure by default

💡 Hint

By default, steps run one after another and stop if one fails.

In declarative pipelines, steps inside a stage run sequentially and if one fails, the stage stops and subsequent steps do not run.

🧠 Conceptual

expert

What is the effect of the 'parallel' directive in Jenkins pipeline?

In Jenkins pipeline, what happens when you use the 'parallel' directive inside a stage?

A Multiple branches run at the same time, speeding up the build

B Branches run one after another in defined order

C Pipeline pauses until all branches complete sequentially

D Pipeline fails immediately

💡 Hint

Parallel means multiple things happen simultaneously.

The 'parallel' directive runs multiple branches concurrently, reducing total build time.