Jenkinsfile concept - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline block.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                [1] 'echo Building...'
            }
        }
    }
}

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

Ash

Bexecute

Crun

Dcommand

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' or 'execute' instead of 'sh' causes errors.

The sh step runs shell commands in Jenkins pipelines.

2fill in blank

medium

Complete the code to specify the agent as a Docker container.

Jenkins

pipeline {
    agent {
        docker {
            image '[1]'
        }
    }
    stages {
        stage('Test') {
            steps {
                sh 'echo Testing...'
            }
        }
    }
}

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

Aubuntu:latest

Bnodejs:12

Cpython:3.8

Dmysql:5.7

Attempts:

3 left

💡 Hint

Common Mistakes

Using an unrelated image like 'mysql:5.7' for a build agent.

The image field specifies the Docker image to use as the agent environment.

3fill in blank

hard

Fix the error in the stage declaration by completing the missing keyword.

Jenkins

pipeline {
    agent any
    stages {
        [1]('Deploy') {
            steps {
                sh 'echo Deploying...'
            }
        }
    }
}

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

Astep

Btask

Cstage

Djob

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'step' or 'job' instead of 'stage' causes syntax errors.

The correct keyword to define a stage is stage.

4fill in blank

hard

Fill both blanks to create a post-build action that always runs a cleanup step.

Jenkins

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                sh 'echo Building...'
            }
        }
    }
    post {
        [1] {
            [2] {
                sh 'echo Cleaning up...'
            }
        }
    }
}

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

Aalways

Bsuccess

Csteps

Dfailure

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'success' instead of 'always' will skip cleanup on failure.

The post block uses conditions like always and inside it the steps block defines commands to run.

5fill in blank

hard

Fill all three blanks to define an environment variable and use it in a shell step.

Jenkins

pipeline {
    agent any
    environment {
        [1] = '[2]'
    }
    stages {
        stage('Print') {
            steps {
                sh 'echo [3]'
            }
        }
    }
}

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

AMY_VAR

BHelloWorld

C$MY_VAR

DGREETING

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable name and reference inconsistently causes empty output.

Define the variable name as MY_VAR, assign it the string HelloWorld, and use $MY_VAR to access it in shell.

Practice

1. What is the main purpose of a Jenkinsfile in Jenkins?

easy

A. To configure Jenkins server settings

B. To define the steps and stages of a build process in code

C. To store Jenkins user credentials securely

D. To create a backup of Jenkins jobs

Solution

1. Step 1: Understand Jenkinsfile role

   A Jenkinsfile is a text file that defines the build process in Jenkins using code.

2. Step 2: Compare options with Jenkinsfile purpose

   Only To define the steps and stages of a build process in code describes defining build steps and stages, which is the Jenkinsfile's main role.

3. Final Answer:

   To define the steps and stages of a build process in code -> Option B

4. Quick Check:

   Jenkinsfile = build process code [OK]

Hint: Jenkinsfile scripts the build steps in code [OK]

Common Mistakes:

• Confusing Jenkinsfile with Jenkins server config
• Thinking Jenkinsfile stores credentials
• Assuming Jenkinsfile is for backup

2. Which of the following is the correct way to start a declarative pipeline in a Jenkinsfile?

easy

A. pipeline {

B. stage {

C. node {

D. build {

Solution

1. Step 1: Recall declarative pipeline syntax

   A declarative pipeline always starts with the keyword pipeline { to define the pipeline block.

2. Step 2: Check other options

   stage { defines a stage inside the pipeline, node { is used in scripted pipelines, and build { is not a valid top-level block.

3. Final Answer:

   pipeline { -> Option A

4. Quick Check:

   Declarative pipeline starts with pipeline { [OK]

Hint: Declarative pipelines always start with 'pipeline {' [OK]

Common Mistakes:

• Starting with stage instead of pipeline
• Using node block in declarative pipeline
• Using invalid block names like build

3. Given this Jenkinsfile snippet, what will be the output in the console?

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        echo 'Hello, Jenkins!'
      }
    }
  }
}

medium

A. pipeline syntax error

B. No output, pipeline skipped

C. Hello, Jenkins!

D. Stage 'Example' failed

Solution

1. Step 1: Analyze the pipeline structure

   The pipeline has one stage named 'Example' with a step that echoes 'Hello, Jenkins!'.

2. Step 2: Understand echo step behavior

   The echo step prints the given message to the Jenkins console output during the build.

3. Final Answer:

   Hello, Jenkins! -> Option C

4. Quick Check:

   echo prints message = Hello, Jenkins! [OK]

Hint: echo prints text to console output [OK]

Common Mistakes:

• Assuming syntax error without checking code
• Thinking pipeline skips stages by default
• Confusing echo with failure

4. Identify the error in this Jenkinsfile snippet:

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean install'
      }
    }
  }
  post {
    always {
      echo 'Build finished'
    }
  }
}

medium

A. sh step requires double quotes instead of single quotes

B. Incorrect placement of post block outside pipeline

C. Missing closing brace for stages block

D. No error, syntax is correct

Solution

1. Step 1: Check block structure

   All blocks (pipeline, stages, stage, steps, post) are properly opened and closed.

2. Step 2: Validate syntax rules

   The post block is correctly placed inside the pipeline block. The sh step accepts single or double quotes.

3. Final Answer:

   No error, syntax is correct -> Option D

4. Quick Check:

   Proper block structure = no syntax error [OK]

Hint: Check matching braces and block placement [OK]

Common Mistakes:

• Assuming post block must be inside stages
• Thinking single quotes cause error in sh step
• Missing braces in nested blocks

5. You want to add a stage in your Jenkinsfile that only runs tests if the branch is 'main'. Which snippet correctly implements this conditional stage?

hard

A. stage('Test') {
when {
branch 'main'
}
steps {
echo 'Running tests'
}
}

B. stage('Test') {
if (env.BRANCH_NAME == 'main') {
steps {
echo 'Running tests'
}
}
}

C. stage('Test') {
steps {
if (branch == 'main') {
echo 'Running tests'
}
}
}

D. stage('Test') {
when {
environment 'main'
}
steps {
echo 'Running tests'
}
}

Solution

1. Step 1: Understand Jenkins conditional syntax

   Declarative pipelines use the when block with branch 'branchName' to conditionally run stages.

2. Step 2: Evaluate each option

   stage('Test') { when { branch 'main' } steps { echo 'Running tests' } } correctly uses when { branch 'main' }. stage('Test') { if (env.BRANCH_NAME == 'main') { steps { echo 'Running tests' } } } uses scripted style inside declarative, which is invalid. stage('Test') { steps { if (branch == 'main') { echo 'Running tests' } } } tries to use if inside steps, which is not supported. stage('Test') { when { environment 'main' } steps { echo 'Running tests' } } uses environment incorrectly.

3. Final Answer:

   stage('Test') { when { branch 'main' } steps { echo 'Running tests' } } -> Option A

4. Quick Check:

   Use when { branch 'name' } for conditional stages [OK]

Hint: Use when { branch 'main' } to run stage conditionally [OK]

Common Mistakes:

• Using if statements inside declarative stages
• Misusing environment instead of branch in when
• Placing condition inside steps block