Jenkins versions and LTS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Jenkins Long-Term Support (LTS) version in a Dockerfile.

Jenkins

FROM jenkins/jenkins:[1]

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

Alts

Bweekly

Clatest

Dstable

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' which points to the newest but possibly unstable version.

Using 'weekly' which is for the latest features but less stable.

The lts tag in the Jenkins Docker image refers to the Long-Term Support version, which is more stable and recommended for production.

2fill in blank

medium

Complete the command to check the installed Jenkins version using the CLI.

Jenkins

java -jar jenkins-cli.jar -s http://localhost:8080 [1]

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

Ahelp

Bstatus

Cinfo

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'status' which shows server status, not version.

Using 'info' which is not a valid Jenkins CLI command.

The version command shows the current Jenkins version installed on the server.

3fill in blank

hard

Fix the error in the Jenkins update command to use the LTS version.

Jenkins

wget https://get.jenkins.io/jenkins-[1].war -O jenkins.war

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

Astable

Blts

Cweekly

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' which may cause instability.

Using 'stable' which is not a valid Jenkins download label.

To download the Long-Term Support version of Jenkins, use lts in the URL.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline that triggers only on LTS version updates.

Jenkins

pipeline {
  agent any
  triggers {
    pollSCM('[1]')
  }
  stages {
    stage('Build') {
      steps {
        echo 'Building Jenkins version [2]'
      }
    }
  }
}

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

AH/15 * * * *

Bweekly

Clts

Ddaily

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'weekly' as version instead of 'lts'.

Using 'daily' which is not a cron expression.

The cron expression H/15 * * * * polls every 15 minutes, and lts specifies the Long-Term Support version.

5fill in blank

hard

Fill all three blanks to define a Jenkins job that checks out code, builds, and echoes the Jenkins LTS version.

Jenkins

pipeline {
  agent any
  stages {
    stage('Checkout') {
      steps {
        git url: '[1]'
      }
    }
    stage('Build') {
      steps {
        sh 'make build'
      }
    }
    stage('Version') {
      steps {
        echo 'Jenkins version: [2]'
        echo 'Using [3] version'
      }
    }
  }
}

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

Ahttps://github.com/jenkinsci/jenkins.git

Blts

CLong-Term Support

Dweekly

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'weekly' instead of 'lts' for the version.

Using a wrong or unrelated Git URL.

The Git URL points to the Jenkins source code repository. The version is labeled 'lts' for Long-Term Support, which is echoed as a friendly name.

Practice

1. What is the main difference between Jenkins LTS and weekly versions?

easy

A. LTS versions are more stable and updated less frequently

B. Weekly versions are more stable than LTS versions

C. LTS versions have fewer features than weekly versions

D. Weekly versions are only for testing and cannot be used in production

Solution

1. Step 1: Understand Jenkins version types

   Jenkins offers two main version types: LTS (Long-Term Support) and weekly releases.

2. Step 2: Compare update frequency and stability

   LTS versions are designed to be stable and receive updates less often, while weekly versions get new features and fixes more frequently but may be less stable.

3. Final Answer:

   LTS versions are more stable and updated less frequently -> Option A

4. Quick Check:

   Stability and update frequency = LTS [OK]

Hint: LTS means stable and slow updates, weekly means fast updates [OK]

Common Mistakes:

• Confusing stability between LTS and weekly
• Thinking weekly versions are for production only
• Assuming LTS has fewer features always

2. Which command correctly checks the Jenkins version installed on a Linux server?

easy

A. jenkins --version

B. jenkins version check

C. jenkins -v

D. java -jar jenkins.war --version

Solution

1. Step 1: Identify Jenkins version check command

   Jenkins runs as a Java application using the jenkins.war file, so checking version uses the java command with the war file.

2. Step 2: Validate correct syntax

   The correct syntax is: java -jar jenkins.war --version. Other options are invalid commands or incorrect flags.

3. Final Answer:

   java -jar jenkins.war --version -> Option D

4. Quick Check:

   Use java -jar jenkins.war --version [OK]

Hint: Use java -jar jenkins.war --version to check Jenkins version [OK]

Common Mistakes:

• Using 'jenkins --version' which is invalid
• Trying 'jenkins -v' which Jenkins does not support
• Typing commands without java or war file

3. If you install Jenkins weekly version and then run java -jar jenkins.war --version, what output should you expect?

medium

A. An error saying version cannot be determined

B. A version number with a date indicating the weekly build

C. The latest LTS version number

D. No output, just returns to prompt

Solution

1. Step 1: Understand output of version command

   The command shows the Jenkins version installed, including build info.

2. Step 2: Identify output for weekly version

   Weekly versions include a date or build number in the version string, unlike LTS which is a stable release number.

3. Final Answer:

   A version number with a date indicating the weekly build -> Option B

4. Quick Check:

   Weekly version output includes date/build info [OK]

Hint: Weekly versions show date in version output [OK]

Common Mistakes:

• Expecting LTS version number for weekly install
• Thinking command returns no output
• Assuming error occurs for weekly versions

4. You installed Jenkins LTS but notice frequent plugin compatibility errors. What is the most likely cause?

medium

A. Running Jenkins without Java installed

B. Installing weekly plugins on LTS Jenkins

C. Using an outdated LTS version with newer plugins

D. Incorrect Jenkins home directory permissions

Solution

1. Step 1: Analyze plugin compatibility issue

   Plugin errors often occur when Jenkins core and plugins versions mismatch.

2. Step 2: Identify cause related to LTS version

   Using an older LTS version while installing newer plugins can cause incompatibility.

3. Final Answer:

   Using an outdated LTS version with newer plugins -> Option C

4. Quick Check:

   Old LTS + new plugins = compatibility errors [OK]

Hint: Match plugin versions with Jenkins core version [OK]

Common Mistakes:

• Blaming weekly plugins on LTS without checking versions
• Ignoring Java installation issues
• Assuming permissions cause plugin errors

5. Your team wants a Jenkins version that balances stability and access to new features for a production environment. Which version strategy is best?

hard

A. Use the latest LTS version and update it every 12 weeks

B. Use the latest weekly version and update plugins weekly

C. Use an old LTS version and never update it

D. Use weekly versions but only update every 6 months

Solution

1. Step 1: Understand production needs

   Production environments need stability but also reasonable updates for security and features.

2. Step 2: Evaluate version strategies

   Latest LTS versions provide tested stability and updating every 12 weeks balances new features and risk.

3. Step 3: Reject risky options

   Weekly versions updated too often can cause instability; old LTS without updates risks security issues.

4. Final Answer:

   Use the latest LTS version and update it every 12 weeks -> Option A

5. Quick Check:

   LTS + regular updates = stable and current [OK]

Hint: Choose LTS with regular updates for production [OK]

Common Mistakes:

• Choosing weekly versions for production without caution
• Never updating Jenkins risking security
• Updating weekly versions too infrequently