[JENKINS-57157] Global Tools fail to update automatic installs

When a tool is upgraded versions or the automatic installer is changed, Jenkins does not update the tool installed on the build agent.  For example, the Sonarqube plugin installs its scanner as a Global Tool with an automatic installer from maven (populated dropdown).  If you change versions, the new version does not overwrite the previous version on the build agent.

Current workaround is to manually delete the tools directory from every build agent when upgrading any tools.

Expected behavior: either install the tool to a version specific directory based on the source (zip file name, maven version, etc) or overwrite the generic directory with whichever version is specified in Global Tool Configuration (either upgrade or downgrade)

---
Originally reported by jeubank, imported from: Global Tools fail to update automatic installs

• assignee: sonarteam
  
• status: Open
  
• priority: Minor
  
• component(s): sonar-plugin, workflow-basic-steps-plugin
  
• label(s): automatic-install, pipeline, sonarqube, tools, update
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251215-220547
  

When a tool is upgraded versions or the automatic installer is changed, Jenkins does not update the tool installed on the build agent.  For example, the Sonarqube plugin installs its scanner as a Global Tool with an automatic installer from maven (populated dropdown).  If you change versions, the new version does not overwrite the previous version on the build agent.


Current workaround is to manually delete the tools directory from every build agent when upgrading any tools.


Expected behavior: either install the tool to a version specific directory based on the source (zip file name, maven version, etc) or overwrite the generic directory with whichever version is specified in Global Tool Configuration (either upgrade or downgrade)

• environment: Jenkins 2.173, Pipeline Basic Steps 2.15, Sonarqube Scanner for Jenkins 2.8.1