Plugin manager reports wrong version when both .hpi and .jpi filenames exist

1 minute readKnowledge base

Issue

I’ve found that if you put the same plugin with both .hpi and .jpi extensions (and with different versions) in JENKINS_HOME/plugins, the .hpi plugin content will be expanded, but the .jpi plugin version will be the one reported under Manage Jenkins → Manage Plugins → Installed.

You may also see an error message such as: "INFO hudson.PluginManager$1$3$1#isDuplicate: Ignoring /Users/USERNAME/jenkins-home/plugins/kubernetes.hpi because /Users/USERNAME/jenkins-home/plugins/kubernetes.jpi is already loaded"

https://issues.jenkins.io/browse/JENKINS-66602

Environment

Resolution

  1. Verify the versions of both the .hpi and the .jpi file.

    • To get the .hpi version go into the folder of the plugin $JENKINS_HOME/plugins/PLUGIN/META-INF/MANIFEST.MF. In the MANIFEST.MF you will see Plugin-Version: listing the .hpi version.

    • To get the .jpi version go to the Plugin Manager of the UI and it will be displayed there.

    • Alternatively, you can unzip each plugin to a temporary directory, and review the META-INF/MANIFEST.MF

  2. Remove the undesired version of either the .hpi or the .jpi from the plugins folder, then restart the instance.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.