Custom update center won't replace the original plugin version in Jenkins update center

69 views
Skip to first unread message

fkp...@gmail.com

unread,
Jun 9, 2017, 2:42:03 AM6/9/17
to Jenkins Developers
Hi,
I've used the following guide:
https://github.com/ikedam/backend-update-center2/wiki/How-to-create-your-own-Jenkins-Update-Center

 to deliver beta versions to our customers (https://hpsa.github.io/JenkinsPluginUpdateCenter/update-center.json).

After several issues  - I've made it work but now, the Jenkins update won't display the plugin bet version unless i specifically delete the official Jenkins update center for few minutes and make Jenkins check the plugins again.

Anybody has a clue or any smarter solution?

Stephen Connolly

unread,
Jun 11, 2017, 3:12:35 AM6/11/17
to jenkin...@googlegroups.com
Somebody "hacked" a solution to a problem with how Jenkins serves UC content by saying: "first mention of plugin short-name wins"

The correct solution would have been to either list all versions of a plugin in a drop-down or other UI element OR eliminate duplicates with the same version.

Basically users need to put your update centre *in front of* the default update centre or the update will not show.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bb04be61-cbcb-4268-97ce-7ad8c85c3e07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone
Reply all
Reply to author
Forward
0 new messages