I'm seeing the plugin-info-macro on Confluence generate wrong plugin version information on https://wiki.jenkins-ci.org/display/JENKINS/Dimensions+Plugin even though it was showing correctly as of yesterday.
This may be because the version shown in the wiki page is what is now listed in http://updates.jenkins-ci.org/update-center.json (which is an old release from 2011), instead of the latest release (October 2014) which is correctly listed in http://updates.jenkins-ci.org/current/update-center.json and http://updates.jenkins-ci.org/update-center.json?version=1.549 (1.549 is version of parent POM I'm now using). Cheers, David. On Thursday, 6 November 2014 15:38:06 UTC, Kohsuke Kawaguchi wrote: > I just checked and it is showing the masthead correctly, so I assume this > was a transient problem. > > 2014-11-06 4:06 GMT-08:00 domi <[email protected] <javascript:>>: > >> This change might have caused issues with the plugin-info-macro on >> confluence. >> *Cannot Load Update Center* >> error 404 loading update-center.json >> >> >> https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin >> >> Domi >> >> >> >> On 06.11.2014, at 07:19, Kohsuke Kawaguchi <[email protected] >> <javascript:>> wrote: >> >> I've just switched over http://updates.jenkins-ci.org/ from the previous >> "v2" layout from the new "v3" layout. To my testing everything is working >> as expected, but if you see any hiccup or regressions in the next few days, >> let me know. >> >> This is a backend change that's invisible from Jenkins instances out >> there. >> >> The main motivation of this change is to serve the "not exactly the >> latest but works with your Jenkins" version of plugins from UC for older >> versions of Jenkins out there. This in turn allows plugin developers to >> adopt newer core features more aggressively, because doing so doesn't cut >> off users of earlier versions. They still see some version available for >> them to install. I'm using JENKINS-6097 >> <https://issues.jenkins-ci.org/browse/JENKINS-6097> to track this. This >> is a pain we started to feel as we try to update plugins to be >> workflow-capable, which requires us to depend on 1.580. >> >> UC v3 attains this goal by generating 8 update sites for different >> version ranges, and use the version Jenkins reports to serve the best site. >> Previously we only had two, one for mainline and the other for LTS. As was >> with v2, The landing URL >> <http://updates.jenkins-ci.org/update-center.json.html> is always the >> same, so that you don't have to change update center config when you move >> from one version to another. >> >> I've captured some more details in here >> <https://github.com/jenkinsci/backend-update-center2/blob/v3/site/README.md> >> if anyone is interested. >> >> -- >> Kohsuke Kawaguchi >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Kohsuke Kawaguchi > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
