[JIRA] [core] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version

19 views
Skip to first unread message

rami.abughazaleh@gmail.com (JIRA)

unread,
Feb 4, 2016, 10:48:02 PM2/4/16
to jenkinsc...@googlegroups.com
Rami Abughazaleh created an issue
 
Jenkins / Bug JENKINS-32793
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 05/Feb/16 3:47 AM
Environment: Jenkins 1.646
Windows Server 2012 R2
Priority: Minor Minor
Reporter: Rami Abughazaleh

POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version.

For example, the latest version of the tfs plugin is 4.0, but I can't install an older version (ex. 3.2):
```
curl -X POST -d "<jenkins><install plugin=\"t...@3.2.0\" /></jenkins>" --header "Content-Type: text/xml" http://192.168.0.175:8080/pluginManager/installNecessaryPlugins
```

The tfs plugin 4.0 is installed anyway.

I don't think any workarounds exist.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

rami.abughazaleh@gmail.com (JIRA)

unread,
Feb 4, 2016, 10:49:01 PM2/4/16
to jenkinsc...@googlegroups.com
Rami Abughazaleh updated an issue
Change By: Rami Abughazaleh
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version.

For example, the latest version of the tfs plugin is 4.0, but I can't install an older version (ex. 3.2):
 ```
{code}
curl -X POST -d "<jenkins><install plugin=\"t...@3.2.0\" /></jenkins>" --header "Content-Type: text/xml" http://192.168.0.175:8080/pluginManager/installNecessaryPlugins
``` {code}

The tfs plugin 4.0 is installed anyway.

I don't think any workarounds exist.

rami.abughazaleh@gmail.com (JIRA)

unread,
Feb 4, 2016, 10:49:01 PM2/4/16
to jenkinsc...@googlegroups.com
Rami Abughazaleh updated an issue
POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version.

For example, the latest version of the tfs plugin is 4.0, but I can't install an older version (ex. 3.2):

{code}
curl -X POST -d "<jenkins><install plugin=\"t...@3.2.0\" /></jenkins>" --header "Content-Type: text/xml" http:// 192.168.0.175 localhost :8080/pluginManager/installNecessaryPlugins

{code}

The tfs plugin 4.0 is installed anyway.

I don't think any workarounds exist.

dbeck@cloudbees.com (JIRA)

unread,
Feb 9, 2016, 10:54:01 AM2/9/16
to jenkinsc...@googlegroups.com
Daniel Beck resolved as Not A Defect
 

This is not a bug.

This URL is intended to receive a job config.xml file, which has included the plugin versions to generate it for some time. We expect that new plugin releases are able to load old job config.xml's, therefore any current version will satisfy a requirement of an older release specified in the job config.xml.
Change By: Daniel Beck
Status: Open Resolved
Resolution: Not A Defect

rami.abughazaleh@gmail.com (JIRA)

unread,
Feb 9, 2016, 2:54:02 PM2/9/16
to jenkinsc...@googlegroups.com
Rami Abughazaleh commented on Bug JENKINS-32793
 
Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version

The reason I want to install an older plugin is because the new version of the plugin caused some issues and we cannot move forward with it until those issues are fixed for example.

Is there a work-around to installing an older version of a plugin programmatically?

Thank you.

dbeck@cloudbees.com (JIRA)

unread,
Feb 9, 2016, 7:08:01 PM2/9/16
to jenkinsc...@googlegroups.com

Jenkins update sites have no metadata on obsolete releases, so this isn't quite this easy.

Jenkins CLI has a command to install/update a plugin that takes a URL as argument.

rami.abughazaleh@gmail.com (JIRA)

unread,
Feb 9, 2016, 7:45:01 PM2/9/16
to jenkinsc...@googlegroups.com

Thank you!

thomas.steinbach@aikq.de (JIRA)

unread,
Mar 22, 2016, 12:41:01 PM3/22/16
to jenkinsc...@googlegroups.com

Daniel Beck The Jenkins CLI does not install dependencies of a PlugIn but the pluginManager does. So do you know a way to install a plugin in a specific version with automatically resolving dependencies? Nevertheless, the version parameter of the pluginManager API is then quite confusing, as it could be void when ignored :/

mail@tknerr.de (JIRA)

unread,
Oct 18, 2016, 8:31:01 PM10/18/16
to jenkinsc...@googlegroups.com

It's 2016 and there is still no way to install a plugin at a specific version (inlcuding it's dependencies) from the commandline?
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

dbeck@cloudbees.com (JIRA)

unread,
Oct 19, 2016, 7:44:02 AM10/19/16
to jenkinsc...@googlegroups.com

It's 2016 and there is still no way to install a plugin at a specific version (inlcuding it's dependencies) from the commandline?

As I wrote above,

Jenkins update sites have no metadata on obsolete releases, so this isn't quite this easy. Jenkins CLI has a command to install/update a plugin that takes a URL as argument.

fakemailred888@gmail.com (JIRA)

unread,
Nov 1, 2018, 12:19:02 PM11/1/18
to jenkinsc...@googlegroups.com
red der commented on Bug JENKINS-32793

I dont understand what this means: 

"This URL is intended to receive a job config.xml file, which has included the plugin versions to generate it for some time. We expect that new plugin releases are able to load old job config.xml's, therefore any current version will satisfy a requirement of an older release specified in the job config.xml."

Its intended to receive a job config.xml? Its being passed a string like this:


"<jenkins><install plugin=\"t...@3.2.0\" /></jenkins>"

Im trying to parse this explanation but so confused where job config.xml fits in here

 

 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

dbeck@cloudbees.com (JIRA)

unread,
Nov 1, 2018, 12:50:05 PM11/1/18
to jenkinsc...@googlegroups.com

Its intended to receive a job config.xml? Its being passed a string like this:


"<jenkins><install plugin=\"t...@3.2.0\" /></jenkins>"
Im trying to parse this explanation but so confused where job config.xml fits in here

That's a clever hack of the API, but not the intended purpose.

You can submit any XML you want, it only cares about the plugin attributes. And those typically appear in Jenkins job config.xml files (potentially build.xml, too lazy to check). The idea is to ease the migration of job configurations (and potentially build data) by ensuring a Jenkins instance is able to read a given XML file.

martin.danjou14@gmail.com (JIRA)

unread,
Jul 20, 2019, 4:25:02 PM7/20/19
to jenkinsc...@googlegroups.com

There is a Google Summer of Code project related to installing plugins from the command line.

martin.danjou14@gmail.com (JIRA)

unread,
Jul 20, 2019, 4:26:01 PM7/20/19
to jenkinsc...@googlegroups.com
Martin d'Anjou edited a comment on Bug JENKINS-32793
There is a Google Summer of Code project related to [ installing plugins from the command line |https://jenkins . io/projects/gsoc/2019/plugin-installation-manager-tool-cli/].

martin.danjou14@gmail.com (JIRA)

unread,
Jul 20, 2019, 9:33:06 PM7/20/19
to jenkinsc...@googlegroups.com
Change By: Martin d'Anjou
Resolution: Not A Defect
Status: Resolved In Review

martin.danjou14@gmail.com (JIRA)

unread,
Jul 20, 2019, 9:33:06 PM7/20/19
to jenkinsc...@googlegroups.com
Martin d'Anjou updated an issue
Change By: Martin d'Anjou
Issue Type: Bug Improvement

martin.danjou14@gmail.com (JIRA)

unread,
Jul 20, 2019, 9:37:03 PM7/20/19
to jenkinsc...@googlegroups.com
Martin d'Anjou updated an issue
Change By: Martin d'Anjou
Issue Type: Improvement Bug

martin.danjou14@gmail.com (JIRA)

unread,
Jul 20, 2019, 9:37:03 PM7/20/19
to jenkinsc...@googlegroups.com
Change By: Martin d'Anjou
Status: In Review Resolved
Resolution: Won't Fix

martin.danjou14@gmail.com (JIRA)

unread,
Jul 21, 2019, 9:02:02 PM7/21/19
to jenkinsc...@googlegroups.com

rami.abughazaleh@gmail.com (JIRA)

unread,
Jul 22, 2019, 12:27:04 AM7/22/19
to jenkinsc...@googlegroups.com

I was originally able to work-around the problem my directly uploading the plugin file to http://localhost:8080/jenkins/pluginManager/uploadPlugin

Someone posted an article with some sample code:

https://chburmeister.github.io/2017/04/08/deploy-specific-versions-of-jenkins-plugins-via-artifactory-caching.html

rami.abughazaleh@gmail.com (JIRA)

unread,
Jul 22, 2019, 12:27:05 AM7/22/19
to jenkinsc...@googlegroups.com
Rami Abughazaleh edited a comment on Bug JENKINS-32793
I was originally able to work-around the problem my by directly uploading the plugin file to [http://localhost:8080/jenkins/pluginManager/uploadPlugin]


Someone posted an article with some sample code:

Reply all
Reply to author
Forward
0 new messages