One of the side-effects of this is that somebody running 1.553 May end up thinking that there's not much benefit in upgrading as all their plugins are "up to date" and it's just a new 1.645 core that is available.
I think we need to start adding a flag to the metadata that says "newer updates available with Jenkins X" (Not much help to older Jenkins, but the sooner we add support, the better) On Thursday, November 6, 2014, Kohsuke Kawaguchi <[email protected]> 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:_e(%7B%7D,'cvml','jenkinsci-dev%[email protected]');> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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.
