Tool auto-installation in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins Tool Auto-Installation: Plugin Installation Output

You configured Jenkins to auto-install the Git plugin. After restarting Jenkins, you run the command jenkins-cli.jar list-plugins. What output confirms the Git plugin was auto-installed successfully?

A git 4.10.0 installed

B git 4.10.0 disabled

C git 4.10.0 not installed

D No plugin named git found

💡 Hint

Look for the plugin name with the status 'installed'.

The output line with 'installed' means Jenkins successfully auto-installed the Git plugin.

❓ Configuration

intermediate

Configuring Jenkins Tool Auto-Installation for JDK

Which snippet correctly configures Jenkins to auto-install JDK 11 using the Jenkins UI tool configuration?

A Add JDK with name 'jdk11' and check 'Install automatically' with installer 'AdoptOpenJDK 11'

B Add JDK with name 'jdk11' without checking 'Install automatically'

C Add JDK with name 'jdk11' and check 'Install automatically' but no installer selected

D Add JDK with name 'jdk11' and check 'Install automatically' with installer 'Oracle JDK 8'

💡 Hint

Auto-install requires selecting an installer for the JDK version.

To auto-install JDK 11, you must enable 'Install automatically' and select the correct installer for JDK 11.

🔀 Workflow

advanced

Jenkins Pipeline Using Auto-Installed Maven

Given Jenkins is configured to auto-install Maven named 'Maven 3.8.6', which pipeline snippet correctly uses this Maven installation to run mvn clean install?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        // Fill in the correct Maven usage here
      }
    }
  }
}

A withEnv(['MAVEN_HOME=Maven 3.8.6']) { sh 'mvn clean install' }

B withMaven(maven: 'Maven 3.8.6') { sh 'mvn clean install' }

C sh 'MAVEN_HOME=Maven 3.8.6 mvn clean install'

D tool name: 'Maven 3.8.6'; sh 'mvn clean install'

💡 Hint

Use the Jenkins pipeline step designed for Maven tool usage.

The 'withMaven' step sets up the environment to use the named Maven installation automatically.

❓ Troubleshoot

advanced

Jenkins Tool Auto-Installation Failure Diagnosis

You configured Jenkins to auto-install NodeJS but builds fail with node: command not found. What is the most likely cause?

A NodeJS plugin is installed but Jenkins was not restarted

B NodeJS version is set but the tool name is missing

C NodeJS is installed but the PATH environment variable is not updated

D NodeJS tool is configured but 'Install automatically' is not checked

💡 Hint

Auto-install requires enabling the install checkbox.

If 'Install automatically' is not checked, Jenkins won't download NodeJS, causing the command not found error.

✅ Best Practice

expert

Best Practice for Managing Jenkins Tool Auto-Installation Versions

What is the best practice to ensure consistent Jenkins tool auto-installation versions across multiple Jenkins agents?

A Manually install tools on each agent and disable auto-installation

B Use environment variables on each agent to specify tool paths

C Define tool versions centrally in Jenkins global tool configuration and use tool names in pipelines

D Hardcode tool installation paths in each pipeline script

💡 Hint

Central management avoids version drift and manual errors.

Centralizing tool versions in Jenkins global config and referencing by name in pipelines ensures consistency and easier maintenance.