JDK configuration in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is JDK in Jenkins?

JDK stands for Java Development Kit. In Jenkins, it is the Java environment Jenkins uses to run builds that require Java.

beginner

How do you add a new JDK in Jenkins?

Go to Jenkins dashboard > Manage Jenkins > Global Tool Configuration > JDK section > Add JDK > Provide a name and either install automatically or specify the path.

intermediate

What does 'Install automatically' mean in Jenkins JDK configuration?

It means Jenkins will download and install the JDK version automatically on the build agents when needed, without manual setup.

beginner

Why is it important to configure JDK correctly in Jenkins?

Because Jenkins needs the right Java version to compile and run Java projects. Wrong JDK can cause build failures or unexpected errors.

intermediate

How can you verify which JDK version Jenkins is using for a build?

Add a build step to run the command java -version. The output shows the JDK version Jenkins uses during the build.

Where do you configure JDK installations in Jenkins?

A Manage Jenkins > System Log

B Manage Jenkins > Global Tool Configuration

C Manage Jenkins > Credentials

D Manage Jenkins > Plugin Manager

JDK installations are configured under Global Tool Configuration in Jenkins.

What happens if you select 'Install automatically' for a JDK in Jenkins?

A Jenkins downloads and installs the JDK on agents as needed

B Jenkins ignores the JDK and uses system default

C Jenkins requires manual JDK installation on agents

D Jenkins disables Java builds

Selecting 'Install automatically' lets Jenkins handle JDK download and installation on build agents.

What command can you add in a Jenkins build step to check the JDK version used?

A java -checkversion

B javac -help

C jdk -check

D java -version

The command 'java -version' prints the JDK version Jenkins is using.

Why might a Jenkins build fail if the JDK is not configured properly?

A Because the build needs the correct Java version to compile and run

B Because Jenkins only supports one JDK version

C Because JDK configuration affects network settings

D Because Jenkins disables builds without JDK

Incorrect JDK version can cause compilation or runtime errors in Java builds.

Can you configure multiple JDK versions in Jenkins?

A Only if you install plugins

B No, only one JDK can be configured

C Yes, Jenkins supports multiple JDK installations

D Only on Linux agents

Jenkins allows configuring multiple JDK versions to use different Java versions for different jobs.

Explain the steps to add and configure a new JDK in Jenkins.

Think about where Jenkins manages tools and how you specify JDK details.

Why is it important to verify the JDK version Jenkins uses during a build?

Consider what happens if Java versions mismatch.

Practice

1.

What is the main purpose of configuring JDK in Jenkins?

easy

A. To configure the Jenkins web interface theme

B. To set the Jenkins user password

C. To tell Jenkins where Java is installed

D. To install Jenkins plugins automatically

Solution

1. Step 1: Understand JDK role in Jenkins

   Jenkins needs Java to run, so it must know where Java is installed.

2. Step 2: Identify the purpose of JDK configuration

   Configuring JDK tells Jenkins the path to Java installations it can use.

3. Final Answer:

   To tell Jenkins where Java is installed -> Option C

4. Quick Check:

   JDK configuration = Java location [OK]

Hint: JDK config points Jenkins to Java location [OK]

Common Mistakes:

• Confusing JDK config with user settings
• Thinking JDK config installs plugins
• Assuming JDK config changes UI appearance

2.

Which of the following is the correct way to add a new JDK in Jenkins global configuration?

1. Go to Manage Jenkins > Global Tool Configuration
2. Click 'Add JDK'
3. Enter a name and JAVA_HOME path
4. Save the configuration

easy

A. Add JDK under Manage Jenkins > Global Tool Configuration with name and path

B. Add JDK under Manage Jenkins > Configure System with only name

C. Add JDK under Manage Jenkins > Plugin Manager with JAVA_HOME path

D. Add JDK under Manage Jenkins > Credentials with name and path

Solution

1. Step 1: Locate correct Jenkins menu

   JDKs are added under Manage Jenkins > Global Tool Configuration.

2. Step 2: Confirm required fields

   You must provide a name and JAVA_HOME path to add a JDK.

3. Final Answer:

   Add JDK under Manage Jenkins > Global Tool Configuration with name and path -> Option A

4. Quick Check:

   JDK setup = Global Tool Configuration + name + path [OK]

Hint: Add JDK in Global Tool Configuration with name and path [OK]

Common Mistakes:

• Trying to add JDK in Plugin Manager or Credentials
• Skipping the JAVA_HOME path
• Adding JDK under Configure System instead

3.

Given this Jenkins pipeline snippet, what JDK version will be used?

pipeline {
  agent any
  tools {
    jdk 'Java_11'
  }
  stages {
    stage('Build') {
      steps {
        sh 'java -version'
      }
    }
  }
}

Assuming Jenkins has JDKs configured as 'Java_8' and 'Java_11'.

medium

A. Java 8 version

B. Java 11 version

C. Default system Java version

D. No Java version, error occurs

Solution

1. Step 1: Identify the JDK specified in pipeline

   The pipeline uses tools { jdk 'Java_11' } which selects the JDK named 'Java_11'.

2. Step 2: Understand Jenkins tool usage

   Jenkins will use the configured JDK named 'Java_11' for the build steps.

3. Final Answer:

   Java 11 version -> Option B

4. Quick Check:

   tools jdk 'Java_11' = Java 11 used [OK]

Hint: Pipeline jdk name matches configured JDK used [OK]

Common Mistakes:

• Assuming default system Java is used ignoring pipeline tools
• Confusing JDK names with versions
• Thinking error occurs if multiple JDKs exist

4.

What is wrong with this Jenkins JDK configuration snippet?

pipeline {
  agent any
  tools {
    jdk 'Java_15'
  }
  stages {
    stage('Test') {
      steps {
        sh 'java -version'
      }
    }
  }
}

Assuming Jenkins has only 'Java_8' and 'Java_11' configured.

medium

A. The pipeline syntax is invalid

B. The agent 'any' is not allowed with JDK tools

C. The shell command 'java -version' is incorrect

D. The JDK name 'Java_15' is not configured in Jenkins

Solution

1. Step 1: Check configured JDK names

   Jenkins only has 'Java_8' and 'Java_11' configured, not 'Java_15'.

2. Step 2: Understand pipeline tool usage

   Using a JDK name not configured causes Jenkins to fail to find the JDK.

3. Final Answer:

   The JDK name 'Java_15' is not configured in Jenkins -> Option D

4. Quick Check:

   JDK name must match configured names [OK]

Hint: JDK name must exist in Jenkins config [OK]

Common Mistakes:

• Assuming pipeline syntax is wrong
• Thinking shell command is invalid
• Believing agent 'any' conflicts with JDK tools

5.

You want Jenkins to automatically install JDK 17 on agents that don't have it. Which configuration option should you use?

hard

A. Configure JDK with 'Install automatically' and select JDK 17 installer

B. Manually install JDK 17 on all agents and configure path in Jenkins

C. Use a shell script step to download and install JDK 17 during build

D. Set JAVA_HOME environment variable globally without JDK config

Solution

1. Step 1: Understand Jenkins automatic JDK installation

   Jenkins can install JDK automatically if configured with 'Install automatically' option.

2. Step 2: Choose correct configuration for JDK 17

   Selecting 'Install automatically' with JDK 17 installer lets Jenkins handle installation on agents.

3. Final Answer:

   Configure JDK with 'Install automatically' and select JDK 17 installer -> Option A

4. Quick Check:

   Automatic JDK install = 'Install automatically' option [OK]

Hint: Use 'Install automatically' to let Jenkins manage JDK installs [OK]

Common Mistakes:

• Manually installing JDK on all agents is time-consuming
• Using shell scripts adds complexity and errors
• Setting JAVA_HOME alone doesn't install JDK