Support to use the latest compatible version for a given plugin and jenkins core about plugin-installation-manager-tool HOT 6 CLOSED

Tiered update sites are used to provide plugin releases compatible with the user-specified core version; there is no reason for anyone to ever access the current/ update site in an installation/deployment scenario. The correct URL for that is always /update-center[.actual].json?version=2.xxx[.y].

Besides that, I don't know enough about how this component works to contribute to this conversation.

from plugin-installation-manager-tool.

you should just always use the update site directly (https://updates.jenkins.io)
We don't direct update site json files to mirrors at all, (even though the mirror's do have the files)

from plugin-installation-manager-tool.

similar to #169

valid requirement and it's a bug.

from plugin-installation-manager-tool.

Hmm this already seems to work?

wget https://get.jenkins.io/war/2.252/jenkins.war
java -jar plugin-management-cli/target/jenkins-plugin-manager-*.jar --plugins workflow-basic-steps  --war jenkins.war -d plugins

Downloading plugin workflow-basic-steps from url: https://updates.jenkins.io/download/plugins/workflow-basic-steps/2.22/workflow-basic-steps.hpi

Basically we use what's called an update site tier (which includes your core version):

curl --location --silent --fail https://updates.jenkins.io/update-center.actual.json?version=2.252 | jq --raw-output '.plugins["workflow-basic-steps"].version'
2.22

$ curl --location --silent --fail https://updates.jenkins.io/update-center.actual.json?version=2.268 | jq --raw-output '.plugins["workflow-basic-steps"].version'
2.23

See more in the update center docs:
https://updates.jenkins.io/#version-specific-update-sites
and
https://github.com/jenkins-infra/update-center2/tree/master/site#dynamic-update-site-tiers

Is this exactly the issue that you hit, or theoretical in some way?

@daniel-beck in case I missed something

from plugin-installation-manager-tool.

the component doesn't current it uses the tiered update sites.

from plugin-installation-manager-tool.

Aha! I see now, thanks for the clarification since I used the current/ update site from one of the mirrors, and it works now by using the default setup:

Although if I use http://mirror.xmission.com/jenkins/updates/update-center.json the issue still persists, so maybe there is something wrong with that particular mirror, while if I use http://mirror.xmission.com/jenkins/updates/stable/update-center.actual.jsonit works.

Other than that, thanks again and sorry for the false alarm.

from plugin-installation-manager-tool.