Jenkins tool Auto-Install Failed - Fix JDK/Maven/Node Installers

The tool step (or a declarative tools {} block) tried to provide a JDK, Maven, Gradle, or Node install and could not. The tool name is not defined in Global Tool Configuration, or the auto-installer could not download/extract the distribution.

What this error means

A build fails with No tool named <name> found, or an installer error while fetching the tool. The step that needed the tool (a Maven/Gradle build) cannot run because the tool path was never set up.

ERROR: No tool named maven-3.9 found
# or an installer failure:
ERROR: Failed to install Maven: java.io.IOException: Failed to download
https://.../apache-maven-3.9.6-bin.zip

Common causes

Tool name not defined in Global Tool Configuration

The name passed to tool/tools {} does not match any tool installation configured under Manage Jenkins → Tools, so Jenkins cannot resolve it.

Auto-installer download/extract failed

The agent could not download the installer (no network egress, blocked URL, proxy) or could not extract it, so the tool is never installed.

How to fix it

Define the tool and reference its exact name

Configure the tool under Manage Jenkins → Tools, then use the same name in the pipeline.

pipeline {
  agent any
  tools { maven 'maven-3.9'; jdk 'temurin-21' }   // names must match Global Tools
  stages { stage('Build') { steps { sh 'mvn -version && mvn package' } } }
}

Fix installer access or pre-bake the tool

1. Ensure agents have egress to the installer URL (or configure the proxy/mirror).
2. Pre-install the tool on the agent image and point the tool config at that path instead of auto-installing.
3. Verify the chosen installer/version matches the agent OS/arch.

How to prevent it

• Keep tool names in tools {} aligned with Global Tool Configuration.
• Pre-bake common tools into agent images to avoid per-build downloads.
• Provide a reachable mirror/proxy for auto-installers on restricted networks.

Related guides