Update center is switched to v3.

[Kohsuke Kawaguchi]

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 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 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 if anyone is interested.

--

Kohsuke Kawaguchi

[Kohsuke Kawaguchi]

Note to myself: to make roll back possible, all the v2 backend jobs are currently just disabled, ant v3 UC is still served from /var/www/updates2.jenkins-ci.org as opposed to /var/www/updates.jenkins-ci.org.

Come back to this in a week, and clean them up to really complete the transition.

--

Kohsuke Kawaguchi

[Stephen Connolly]

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)

--
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.
For more options, visit https://groups.google.com/d/optout.

--
Sent from my phone

[domi]

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

[Jesse Glick]

On Thu, Nov 6, 2014 at 3:24 AM, Stephen Connolly
<stephen.al...@gmail.com> wrote:
> 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.

Is this a real risk? If I am running Ubuntu 10.04 LTS, I am not going
to see very many updates offered from apt-get upgrade. But I am not
likely to interpret that as meaning that the community of Linux
software developers has gone on sabbatical.

[Jesse Glick]

On Thu, Nov 6, 2014 at 7:06 AM, domi <do...@fortysix.ch> wrote:
> This change might have caused issues with the plugin-info-macro on confluence.

While we are on the topic, it would be nice if this macro were updated to

· Note the availability of any newer alpha/beta release, not just the
latest “stable” release.
· List the latest release for each update center line.

[Kohsuke Kawaguchi]

I just checked and it is showing the masthead correctly, so I assume this was a transient problem.

--

Kohsuke Kawaguchi

[David Conneely]

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.

[Kohsuke Kawaguchi]

Someone told me that junit 1.2 is not downloadable, and from that report I've discovered that http://mirrors.jenkins-ci.org/plugins/ is not properly updated.

I'm working on the fix right now.

--

Kohsuke Kawaguchi

[Kanstantsin Shautsou]

Updated https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter. 

Kohsuke, please update this instructions if you know new issues with v3. 

[Kaz Nishimura]

If I follow the http://updates.jenkins-ci.org/update-center.json link with a normal browser, it redirects to the 1.532 version.  It looks like it does not include some newer plugins.

[Jesse Glick]

On Sun, Nov 16, 2014 at 12:05 AM, Kaz Nishimura <kaz...@vx68k.org> wrote:
> If I follow the http://updates.jenkins-ci.org/update-center.json link with a
> normal browser, it redirects to the 1.532 version.

Right, you need to append

?version=1.580.1

or whatever you want, like Jenkins itself would send. The fallback
behavior is to show 1.532.x-compatible plugins.

[Kohsuke Kawaguchi]

I've fixed INFRA-196, so it should now correctly refer to the latest update center, not the oldest.

--
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.
For more options, visit https://groups.google.com/d/optout.

--

Kohsuke Kawaguchi

[Björn Pedersen]

Just one thing: The version number for the lates war-file is not updated on the web frontpage at jenkins-ci.org ( available is 1.590, but 1.588 is still announced)

Björn

[Daniel Beck]

I fixed INFRA-208 by pointing the "latest release" block on the site to /var/www/updates2.jenkins-ci.org. Please change that back when completing the migration.