Jenkins in the CI/CD ecosystem - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Jenkins in the context of CI/CD?

Jenkins is an open-source automation server that helps automate parts of software development like building, testing, and deploying code, making continuous integration and continuous delivery easier.

beginner

How does Jenkins fit into the CI/CD pipeline?

Jenkins acts as the central tool that runs automated tasks such as compiling code, running tests, and deploying applications, connecting developers' code changes to production quickly and safely.

beginner

What is a Jenkins 'job' or 'pipeline'?

A Jenkins job or pipeline is a set of instructions that tells Jenkins what steps to perform, like building code, running tests, and deploying software automatically.

intermediate

Why is Jenkins popular in DevOps?

Jenkins is popular because it is free, easy to extend with many plugins, supports many languages and tools, and helps teams deliver software faster by automating repetitive tasks.

intermediate

Name two key features of Jenkins that support CI/CD.

1. Automated build and test execution on code changes. 2. Integration with many tools and plugins for deployment and notifications.

What is the main purpose of Jenkins in CI/CD?

A Design user interfaces

B Automate software build, test, and deployment processes

C Manage project documentation

D Write application code

Jenkins automates building, testing, and deploying software, which is the core of CI/CD.

Which of these is a Jenkins pipeline?

A A set of automated steps to build and deploy software

B A network cable

C A database schema

D A user interface design

A Jenkins pipeline defines the automated steps for building, testing, and deploying software.

How does Jenkins notify developers about build results?

A By printing paper reports

B By changing the code automatically

C Through emails or messaging tools using plugins

D By updating the project documentation

Jenkins uses plugins to send notifications via email or chat tools to inform developers about build status.

Which of the following is NOT a Jenkins feature?

A Plugin support

B Continuous deployment

C Automated testing

D Code editing

Jenkins does not provide code editing; it automates build and deployment tasks.

What type of tool is Jenkins?

A Automation server

B Database management system

C Text editor

D Operating system

Jenkins is an automation server used to automate software development tasks.

Explain how Jenkins helps in the continuous integration and continuous delivery process.

Think about how Jenkins connects code changes to delivery.

Describe what a Jenkins pipeline is and why it is important.

Consider the instructions Jenkins follows to automate tasks.

Practice

1. What is the primary role of Jenkins in the CI/CD ecosystem?

easy

A. Automate building, testing, and deploying software

B. Write application code

C. Design user interfaces

D. Manage database schemas

Solution

1. Step 1: Understand Jenkins purpose

   Jenkins is a tool designed to automate software processes like building, testing, and deployment.

2. Step 2: Compare options with Jenkins role

   Only Automate building, testing, and deploying software matches Jenkins' automation role in CI/CD; others relate to unrelated tasks.

3. Final Answer:

   Automate building, testing, and deploying software -> Option A

4. Quick Check:

   Jenkins automates CI/CD tasks = A [OK]

Hint: Jenkins automates software delivery steps [OK]

Common Mistakes:

• Confusing Jenkins with coding or UI design tools
• Thinking Jenkins manages databases
• Assuming Jenkins writes application code

2. Which of the following is the correct syntax to define a simple Jenkins pipeline in a Jenkinsfile?

easy

A. job {
steps {
echo 'Building...'
}
}

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

C. pipeline: {
stage('Build') {
echo 'Building...'
}
}

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

Solution

1. Step 1: Review Jenkins pipeline syntax

   The correct Jenkins pipeline uses the 'pipeline' block with 'agent' and 'stages' sections.

2. Step 2: Match syntax with options

   pipeline { agent any stages { stage('Build') { steps { echo 'Building...' } } } } correctly shows the pipeline structure with agent, stages, and steps. Others have invalid or incomplete syntax.

3. Final Answer:

   Correct Jenkins pipeline syntax with agent and stages -> Option D

4. Quick Check:

   Valid Jenkinsfile uses 'pipeline' block = D [OK]

Hint: Look for 'pipeline', 'agent', and 'stages' keywords [OK]

Common Mistakes:

• Missing 'agent' block in pipeline
• Using 'build' or 'job' instead of 'pipeline'
• Incorrect block nesting or missing braces

3. Given this Jenkins pipeline snippet, what will be the output when the pipeline runs?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        echo 'Starting tests'
        script {
          def result = 2 + 3
          echo "Result is ${result}"
        }
      }
    }
  }
}

medium

A. Starting tests
Result is ${result}

B. Starting tests
Result is 5

C. Starting tests
Result is 23

D. Syntax error in pipeline

Solution

1. Step 1: Understand pipeline script block execution

   The 'script' block allows Groovy code execution; 'def result = 2 + 3' calculates 5.

2. Step 2: Analyze echo statements

   First echo prints 'Starting tests', second prints 'Result is 5' using string interpolation.

3. Final Answer:

   Starting tests Result is 5 -> Option B

4. Quick Check:

   Groovy evaluates expressions inside ${} = C [OK]

Hint: Groovy evaluates ${} inside double quotes [OK]

Common Mistakes:

• Treating ${result} as plain text
• Concatenating numbers as strings
• Assuming syntax error due to script block

4. You have this Jenkins pipeline snippet:

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

What is the problem with this pipeline?

medium

A. Multiple 'stages' blocks are not allowed in one pipeline

B. Missing 'agent' declaration

C. Echo commands are invalid in Jenkinsfile

D. Pipeline must have at least three stages

Solution

1. Step 1: Review pipeline structure rules

   A Jenkins pipeline can have only one 'stages' block containing multiple 'stage' blocks.

2. Step 2: Identify error in given pipeline

   Here, there are two separate 'stages' blocks, which is invalid syntax.

3. Final Answer:

   Multiple 'stages' blocks are not allowed in one pipeline -> Option A

4. Quick Check:

   Only one 'stages' block per pipeline = B [OK]

Hint: Only one 'stages' block allowed in Jenkinsfile [OK]

Common Mistakes:

• Thinking multiple 'stages' blocks are valid
• Confusing missing agent with stages error
• Assuming echo commands cause errors

5. You want to create a Jenkins pipeline that builds your project only if the branch is 'main' and runs tests on all branches. Which pipeline snippet correctly implements this logic?

pipeline {
  agent any
  stages {
    stage('Build') {
      when {
        branch 'main'
      }
      steps {
        echo 'Building main branch'
      }
    }
    stage('Test') {
      steps {
        echo 'Running tests'
      }
    }
  }
}

hard

A. The pipeline builds and tests only on 'main' branch

B. The pipeline builds on all branches and tests only on 'main'

C. The pipeline builds only on 'main' branch and tests on all branches as required

D. The pipeline builds and tests on all branches without conditions

Solution

1. Step 1: Understand 'when' condition in Build stage

   The 'when { branch 'main' }' condition restricts the Build stage to run only on the 'main' branch.

2. Step 2: Analyze Test stage behavior

   The Test stage has no 'when' condition, so it runs on all branches.

3. Final Answer:

   The pipeline builds only on 'main' branch and tests on all branches as required -> Option C

4. Quick Check:

   'when' limits build; test runs always = A [OK]

Hint: Use 'when' to limit stages by branch [OK]

Common Mistakes:

• Assuming all stages run on all branches
• Misplacing 'when' condition on Test stage
• Confusing branch names or conditions