What is Continuous Integration in Jenkins - Interactive Quiz & Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline that triggers on every code commit.

Jenkins

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

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

Atimer

Bcron

CmanualTrigger

DpollSCM

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing cron triggers a build on a schedule, not on code changes.

manualTrigger is not a valid Jenkins trigger.

The pollSCM trigger tells Jenkins to check the source code repository for changes regularly, enabling continuous integration by building on every commit.

2fill in blank

medium

Complete the Jenkins pipeline stage to run tests after building the code.

Jenkins

stage('Test') {
  steps {
    sh '[1]'
  }
}

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

Anpm test

Bnpm deploy

Cnpm build

Dnpm start

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'npm start' runs the app, not tests.

Using 'npm build' compiles but does not test.

The command npm test runs the test scripts defined in the project, which is essential in continuous integration to verify code correctness after building.

3fill in blank

hard

Fix the error in the Jenkinsfile snippet to archive test results correctly.

Jenkins

post {
  always {
    [1] artifacts: 'test-results/*.xml', allowEmptyArchive: true
  }
}

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

AsaveArtifacts

BarchiveFiles

CarchiveArtifacts

DstoreArtifacts

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'archiveFiles' or 'saveArtifacts' are not valid Jenkins steps.

Misspelling the step name causes pipeline errors.

The correct Jenkins pipeline step to save build artifacts is archiveArtifacts. This archives files like test reports for later review.

4fill in blank

hard

Fill both blanks to define environment variables and use them in the build stage.

Jenkins

pipeline {
  agent any
  environment {
    APP_NAME = '[1]'
  }
  stages {
    stage('Build') {
      steps {
        echo "Building $[2]"
      }
    }
  }
}

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

AMyApp

BYourApp

CAPP_NAME

DBuild

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the app name directly in echo instead of variable.

Using undefined variable names.

Setting APP_NAME to 'MyApp' defines the variable. Using APP_NAME inside echo prints the app name dynamically during build.

5fill in blank

hard

Fill all three blanks to create a post-build action that sends notifications on failure.

Jenkins

post {
  failure {
    [1] {
      subject: '[2] Build Failed',
      body: 'Please check the [3] logs for details.'
    }
  }
}

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

Aemailext

BJenkins

Cbuild

Demail

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'email' instead of 'emailext' causes errors.

Incorrect subject or body placeholders.

The emailext step sends emails. The subject uses 'Jenkins' as the sender or system name. The body refers to 'build' logs to guide the user.

Practice

1. What is the main goal of Continuous Integration (CI) in software development?

easy

A. To write code without any collaboration

B. To deploy code directly to production without testing

C. To merge code changes frequently and test them automatically

D. To manually test code after all features are complete

Solution

1. Step 1: Understand the purpose of Continuous Integration

   Continuous Integration means developers merge their code changes often to avoid conflicts and detect errors early.

2. Step 2: Identify the key activity in CI

   Automatic testing after merging helps catch problems quickly and keeps the codebase healthy.

3. Final Answer:

   To merge code changes frequently and test them automatically -> Option C

4. Quick Check:

   CI = Frequent merge + automatic test [OK]

Hint: CI means frequent merges with automatic tests [OK]

Common Mistakes:

• Thinking CI means skipping tests
• Believing CI is only about deployment
• Assuming CI means no collaboration

2. Which Jenkins feature is commonly used to implement Continuous Integration pipelines?

easy

A. Jenkins Executor

B. Jenkins Agent

C. Jenkins Node

D. Jenkinsfile

Solution

1. Step 1: Identify Jenkins components related to pipelines

   Jenkinsfile is a text file that defines the steps of a CI pipeline in code form.

2. Step 2: Understand the role of Jenkinsfile in CI

   It allows automation of build, test, and deploy steps, making CI repeatable and consistent.

3. Final Answer:

   Jenkinsfile -> Option D

4. Quick Check:

   Pipeline code = Jenkinsfile [OK]

Hint: Pipeline code lives in Jenkinsfile [OK]

Common Mistakes:

• Confusing Jenkinsfile with Jenkins Agent
• Thinking Jenkins Node defines pipeline steps
• Mixing Jenkins Executor with pipeline definition

3. Given this Jenkins pipeline snippet:

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

What will Jenkins output during the 'Test' stage?

medium

A. Testing...

B. Building...

C. Build and Test

D. No output

Solution

1. Step 1: Read the pipeline stages and steps

   The 'Test' stage contains a step that echoes 'Testing...'.

2. Step 2: Understand Jenkins output behavior

   During the 'Test' stage, Jenkins runs the echo command and outputs 'Testing...'.

3. Final Answer:

   Testing... -> Option A

4. Quick Check:

   Test stage echo = 'Testing...' [OK]

Hint: Echo inside stage prints that stage's message [OK]

Common Mistakes:

• Confusing output of Build stage with Test stage
• Expecting combined output in one stage
• Thinking no output appears without explicit print

4. You wrote this Jenkins pipeline snippet:

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

What is the error and how to fix it?

medium

A. Missing agent declaration; add 'agent any'

B. Typo in 'ech' command; change to 'echo'

C. Stages block is missing; add 'stages' keyword

D. No error; pipeline is correct

Solution

1. Step 1: Identify the incorrect command in the Test stage

   The command 'ech' is not valid; it should be 'echo' to print text.

2. Step 2: Correct the typo to fix the pipeline

   Changing 'ech' to 'echo' will allow Jenkins to run the Test stage without errors.

3. Final Answer:

   Typo in 'ech' command; change to 'echo' -> Option B

4. Quick Check:

   Command typo fixed by 'echo' [OK]

Hint: Check spelling of commands carefully [OK]

Common Mistakes:

• Ignoring typo and expecting pipeline to run
• Adding unnecessary agent block
• Misunderstanding stages block presence

5. You want to set up a Jenkins pipeline that automatically builds and tests your code every time a developer pushes changes. Which two steps are essential to implement Continuous Integration correctly?

hard

A. Write a Jenkinsfile defining build and test stages; configure Jenkins to trigger on code push

B. Manually run builds after code is merged; deploy to production immediately

C. Write a Jenkinsfile with only deployment steps; ignore tests

D. Use Jenkins only for deployment; test code locally

Solution

1. Step 1: Define automated build and test in Jenkinsfile

   Continuous Integration requires automated steps to build and test code on every change.

2. Step 2: Configure Jenkins to trigger pipeline on code push

   Automatic triggering ensures CI runs without manual intervention, catching issues early.

3. Final Answer:

   Write a Jenkinsfile defining build and test stages; configure Jenkins to trigger on code push -> Option A

4. Quick Check:

   CI needs automation + trigger on push [OK]

Hint: Automate build/test and trigger on push [OK]

Common Mistakes:

• Skipping tests in pipeline
• Running builds manually
• Using Jenkins only for deployment