When to choose Jenkins - Interactive Code Practice

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'

Aexecute

Bsh

Crun

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.

2fill in blank

medium

Complete the code to trigger a Jenkins job remotely using a token.

Jenkins

curl -X POST http://jenkins.example.com/job/myjob/build?token=[1]

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

Amytoken123

Bpassword

Cusername

Dapikey

Attempts:

3 left

💡 Hint

Common Mistakes

Using username or password instead of token.

The token mytoken123 is used to authenticate remote triggers.

3fill in blank

hard

Fix the error in the Jenkinsfile to correctly define an environment variable.

Jenkins

pipeline {
  agent any
  environment {
    MY_VAR = [1]
  }
  stages {
    stage('Test') {
      steps {
        sh 'echo $MY_VAR'
      }
    }
  }
}

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

A'hello'

Bhello

C"hello"

DMY_VAR

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted values or single quotes which may cause errors.

Environment variables in Jenkinsfile need to be strings with double quotes.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline stage that runs only on the 'main' branch.

Jenkins

stage('Deploy') {
  when {
    [1] 'main'
  }
  steps {
    [2] 'echo Deploying to production'
  }
}

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

Abranch

Bsh

CnotEquals

Dbat

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'notEquals' or 'bat' which are incorrect here.

The when { branch 'main' } condition uses branch to check the branch. The sh step runs shell commands.

5fill in blank

hard

Fill all three blanks to define a Jenkins pipeline with a parameter and use it in a stage.

Jenkins

pipeline {
  agent any
  parameters {
    string(name: '[1]', defaultValue: 'world', description: 'Who to greet')
  }
  stages {
    stage('Greet') {
      steps {
        sh "echo Hello, [2]!"
      }
    }
  }
  environment {
    GREETING = '[3]'
  }
}

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

ANAME

B${params.NAME}

C"world"

DUSER

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong parameter names or missing parameter syntax.

The parameter name is NAME. To use it in shell, use ${params.NAME}. The environment variable GREETING is set to the default world.

Practice

1. Which situation best describes when you should choose Jenkins for your project?

easy

A. When you want to design graphics for your application

B. When you only need to write code without any automation

C. When you want to manually test software without any tools

D. When you want to automate building, testing, and deploying software regularly

Solution

1. Step 1: Understand Jenkins purpose

   Jenkins is designed to automate software building, testing, and deployment tasks.

2. Step 2: Match Jenkins use case

   Choosing Jenkins fits when you want to automate these repetitive tasks for faster delivery.

3. Final Answer:

   When you want to automate building, testing, and deploying software regularly -> Option D

4. Quick Check:

   Automation need = Jenkins use [OK]

Hint: Pick Jenkins when automation of build and deploy is needed [OK]

Common Mistakes:

• Thinking Jenkins is for manual testing only
• Confusing Jenkins with coding or design tools
• Using Jenkins without automation goals

2. Which Jenkins feature is essential for continuous integration?

easy

A. Manual code review

B. Automated build triggers on code changes

C. Graphic design tools

D. Manual deployment steps

Solution

1. Step 1: Identify continuous integration key feature

   Continuous integration requires automatic builds when code changes happen.

2. Step 2: Match Jenkins feature

   Jenkins triggers builds automatically on code commits, enabling continuous integration.

3. Final Answer:

   Automated build triggers on code changes -> Option B

4. Quick Check:

   Auto build trigger = Continuous integration [OK]

Hint: Look for automation on code changes for CI [OK]

Common Mistakes:

• Choosing manual steps instead of automated triggers
• Confusing design tools with Jenkins features
• Ignoring build automation importance

3. What will Jenkins do when configured with a pipeline that triggers on every git push?

medium

A. Run the pipeline steps automatically after each push

B. Send an email without running any build

C. Ignore the push and do nothing

D. Delete the pushed code from the repository

Solution

1. Step 1: Understand pipeline trigger on git push

   When Jenkins pipeline is set to trigger on git push, it activates after each code push.

2. Step 2: Identify Jenkins behavior

   Jenkins runs the defined pipeline steps automatically after detecting the push event.

3. Final Answer:

   Run the pipeline steps automatically after each push -> Option A

4. Quick Check:

   Pipeline trigger on push = automatic run [OK]

Hint: Pipeline triggers run automatically on git push [OK]

Common Mistakes:

• Thinking Jenkins ignores git pushes
• Assuming Jenkins deletes code on push
• Confusing email notifications with pipeline runs

4. You set Jenkins to build your project but it never starts after code changes. What is the likely problem?

medium

A. Build trigger is not configured to watch code changes

B. Jenkins server is running normally

C. Code changes are automatically built

D. Pipeline script has no syntax errors

Solution

1. Step 1: Check build trigger configuration

   If Jenkins does not start builds after code changes, triggers may be missing or misconfigured.

2. Step 2: Confirm trigger absence causes no build

   Without triggers, Jenkins won't detect changes to start builds automatically.

3. Final Answer:

   Build trigger is not configured to watch code changes -> Option A

4. Quick Check:

   Missing trigger = no build start [OK]

Hint: Verify build triggers to fix no-build issue [OK]

Common Mistakes:

• Assuming Jenkins builds without triggers
• Ignoring trigger settings in Jenkins
• Confusing server status with build triggers

5. Your team wants to speed up software delivery with automated tests and deployments. Which Jenkins setup is best?

hard

A. Deploy code without any testing to save time

B. Manually run tests and deploy after each code change

C. Create a pipeline that builds code, runs tests, and deploys on success

D. Use Jenkins only for code storage without automation

Solution

1. Step 1: Identify automation needs

   The team wants faster delivery with automated tests and deployments to reduce manual work.

2. Step 2: Choose Jenkins pipeline setup

   A pipeline that builds, tests, and deploys automatically fits this goal perfectly.

3. Final Answer:

   Create a pipeline that builds code, runs tests, and deploys on success -> Option C

4. Quick Check:

   Automated pipeline = faster delivery [OK]

Hint: Automate build, test, deploy in one pipeline [OK]

Common Mistakes:

• Skipping automation and doing manual steps
• Using Jenkins only as code storage
• Deploying without testing risks errors