Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Duplicate
-
None
Description
Using Jenkins 1.642.4, I installed an older version of my plugin from a hpi file using the Jenkins CLI and did a safe restart. When I try to install a newer version of the same plugin using the Jenkins CLI, http://localhost:8080/pluginManager/installed still shows the older version is installed even after a safe restart.
Manually uploading the files to the server works fine, I can upgrade/downgrade and install any specific version without trouble. There is only an issue when I use the Jenkins CLI
When installing a plugin manually, it creates a
{plugin-name}.bak
file but when I use the CLI it creates a
{plugin-name}-{version}.bak
I assume this might be the cause of the issue
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
Activity
java -jar jenkins-cli.jar -s http://localhost:8080/ install-plugin hub-jenkins-1.5.3-SNAPSHOT.hpi
followed by
java -jar jenkins-cli.jar -s http://localhost:8080/ safe-restart
The -name argument lets you override the automatically determined plugin name based on the file name.
Since the plugin has a different file name, it gets installed in addition to the regular one, and then they probably clash, and the wrong one is loaded or something.
Thank you danielbeck using the -name argument solves the issue we are having and everything works as expected now
Behavior remains stupid, so let's keep it around as a low priority bug.
what's the full command line for the CLI you use? No placeholders, everything verbatim including plugin file name.