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.