Why Jenkins for automation - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a Jenkins pipeline with a simple stage.

Jenkins

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

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

Ash

Brun

Cexecute

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' or 'execute' which are not Jenkins pipeline steps.

The sh step runs shell commands in Jenkins pipelines. It is used here to print a message.

2fill in blank

medium

Complete the code to trigger a Jenkins job automatically after a code push.

Jenkins

pipeline {
  triggers {
    [1] 'H/5 * * * *'
  }
  stages {
    stage('Test') {
      steps {
        sh 'echo Testing...'
      }
    }
  }
}

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

Aschedule

Bcron

CpollSCM

Dtimer

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'cron' or 'timer' which are not Jenkins triggers for SCM polling.

pollSCM tells Jenkins to check the source code repository regularly for changes and trigger the job if changes are found.

3fill in blank

hard

Fix the error in the Jenkins pipeline code to archive build artifacts.

Jenkins

pipeline {
  agent any
  stages {
    stage('Archive') {
      steps {
        archiveArtifacts artifacts: '[1]'
      }
    }
  }
}

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

A'**/*.txt'

B'build.log'

C'src/*.java'

D'**/*.jar'

Attempts:

3 left

💡 Hint

Common Mistakes

Using patterns that do not match build outputs like source code or logs.

The pattern '**/*.jar' archives all jar files in any folder, which is common for build artifacts.

4fill in blank

hard

Fill both blanks to define environment variables and use them in a Jenkins pipeline.

Jenkins

pipeline {
  agent any
  environment {
    GREETING = [1]
  }
  stages {
    stage('Say Hello') {
      steps {
        sh 'echo [2]'
      }
    }
  }
}

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

A'Hello, Jenkins!'

B$GREETING

CGREETING

D'Hi there!'

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable name without $ in shell command, or missing quotes in environment value.

Environment variables are set with a string value like 'Hello, Jenkins!' and accessed in shell steps with $GREETING.

5fill in blank

hard

Fill all three blanks to create a Jenkins pipeline that builds, tests, and deploys with proper stages.

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh '[1]'
      }
    }
    stage('Test') {
      steps {
        sh '[2]'
      }
    }
    stage('Deploy') {
      steps {
        sh '[3]'
      }
    }
  }
}

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

Amake build

Bmake test

Cmake deploy

Dmake clean

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'make clean' in build or deploy stages, or mixing order of commands.

The typical pipeline runs make build to compile, make test to run tests, and make deploy to deploy the app.

Practice

1. Why is Jenkins commonly used for automation in software development?

easy

A. It is a tool for designing user interfaces.

B. It is a programming language for writing software.

C. It is a database management system.

D. It automates repetitive tasks to save time and reduce errors.

Solution

1. Step 1: Understand Jenkins purpose

   Jenkins is designed to automate repetitive software tasks like building and testing.

2. Step 2: Compare options to Jenkins role

   Options B, C, and D describe unrelated tools or roles, not automation.

3. Final Answer:

   It automates repetitive tasks to save time and reduce errors. -> Option D

4. Quick Check:

   Jenkins automates tasks = A [OK]

Hint: Jenkins automates tasks, not coding or databases [OK]

Common Mistakes:

• Confusing Jenkins with a programming language
• Thinking Jenkins manages databases
• Assuming Jenkins designs UI

2. Which of the following is the correct way to define a simple Jenkins pipeline step?

easy

A. pipeline { stages { stage('Build') { steps { echo 'Building...' } } } }

B. build { pipeline { echo 'Building...' } }

C. stage { pipeline { steps { echo 'Building...' } } }

D. steps { pipeline { stage('Build') { echo 'Building...' } } }

Solution

1. Step 1: Recall Jenkins pipeline syntax

   The correct syntax uses 'pipeline' with 'stages', each having 'stage' and 'steps'.

2. Step 2: Match syntax to options

   pipeline { stages { stage('Build') { steps { echo 'Building...' } } } } matches the correct structure; others misuse keywords or nesting.

3. Final Answer:

   pipeline { stages { stage('Build') { steps { echo 'Building...' } } } } -> Option A

4. Quick Check:

   Correct pipeline syntax = D [OK]

Hint: Look for 'pipeline', 'stages', 'stage', then 'steps' order [OK]

Common Mistakes:

• Misplacing 'pipeline' inside 'build' or 'stage'
• Omitting 'stages' block
• Incorrect nesting of steps

3. How does Jenkins help teams deliver software faster and more reliably?

easy

A. By automating build, test, and deployment steps in pipelines.

B. By replacing developers with AI to write code automatically.

C. By manually running tests and deployments on demand.

D. By storing all source code in a central database.

Solution

1. Step 1: Identify Jenkins automation benefits

   Jenkins automates repetitive tasks like building, testing, and deploying software.

2. Step 2: Eliminate incorrect options

   By replacing developers with AI to write code automatically. is false; Jenkins does not replace developers. By manually running tests and deployments on demand. is manual, not automated. By storing all source code in a central database. describes version control, not Jenkins automation.

3. Final Answer:

   By automating build, test, and deployment steps in pipelines. -> Option A

4. Quick Check:

   Automation speeds delivery = A [OK]

Hint: Automation of build-test-deploy speeds delivery [OK]

Common Mistakes:

• Thinking Jenkins writes code automatically
• Confusing manual and automated processes
• Mixing Jenkins with version control systems

4. Given this Jenkins pipeline snippet, what will be printed during the 'Test' stage?

pipeline {
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
    stage('Test') {
      steps {
        echo 'Testing...'
      }
    }
  }
}

medium

A. Building...

B. Testing... Building...

C. Testing...

D. Building... Testing...

Solution

1. Step 1: Understand pipeline stage order

   Stages run sequentially: first 'Build', then 'Test'. Each prints its own echo.

2. Step 2: Identify output specific to 'Test' stage

   During the 'Test' stage, only echo 'Testing...' executes and prints 'Testing...'.

3. Final Answer:

   Testing... -> Option C

4. Quick Check:

   Test stage output = D [OK]

Hint: Stages run in order; output concatenates their echoes [OK]

Common Mistakes:

• Assuming stages run in parallel
• Only printing last stage output
• Mixing stage order

5. Identify the error in this Jenkins pipeline snippet:

pipeline {
  stages {
    stage('Deploy') {
      steps {
        sh 'deploy.sh'
      }
      post {
        always {
          echo 'Cleanup done'
        }
      }
    }
  }
}

medium

A. The 'post' block must be inside the 'pipeline' block but outside 'stages'.

B. The 'post' block must be inside the 'stage' block.

C. The 'sh' command is invalid inside 'steps'.

D. The 'always' block cannot be used in Jenkins pipelines.

Solution

1. Step 1: Check 'post' block placement rules

   In declarative pipelines, 'post' blocks can be placed inside 'pipeline' or inside individual 'stage' blocks.

2. Step 2: Verify snippet structure

   Here, 'post' is correctly placed inside the 'stage('Deploy')' block, which is valid.

3. Step 3: Identify the actual error

   The snippet is valid; no error in 'post' placement. The 'post' block inside 'stage' is allowed.

4. Final Answer:

   The 'post' block must be inside the 'stage' block. -> Option B

5. Quick Check:

   'post' block placement inside 'stage' is valid = A [OK]

Hint: 'post' blocks can be inside 'pipeline' or 'stage' blocks [OK]

Common Mistakes:

• Placing 'post' outside 'pipeline'
• Thinking 'sh' is invalid in 'steps'
• Believing 'always' is not allowed