Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11977 (closed)

Opened 10 years ago

Closed 10 years ago

Bug: Updater is using invalid jenkins URL

Reported by: rleigh Owned by: mlinkert
Priority: critical Milestone: 5.0.0
Component: Bio-Formats Version: 5.0.0-beta2-RC3
Keywords: n.a. Cc: Sharmon.Lebby@…, jamoore, ajpatterson
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

See this mail:
http://lists.openmicroscopy.org.uk/pipermail/ome-users/2014-February/004202.html

The loci.plugins Updater is trying to fetch the update from this URL:
http://ci.openmicroscopy.org/job/BIOFORMATS-5.0-latest/lastSuccessfulBuild/artifact/trunk/artifacts/loci_tools.jar
but it doesn't exist.

We should never break updates.
Can we insert redirects for the potential URLs the updater will use?
Does the updater itself need to use different URLs?
Could the updater use stable non-jenkins URLs from downloads.openmicroscopy.org?

Change History (2)

comment:1 Changed 10 years ago by mlinkert

  • Priority changed from blocker to critical

So far as I can see, this has been fixed for some time - dev_5_0 currently pulls from http://ci.openmicroscopy.org/job/BIOFORMATS-5.0-latest/lastSuccessfulBuild/artifact/artifacts/loci_tools.jar. I haven't so far been able to find which revision would have caused this (unless there is something funny going on with one of the redirects going to the wrong place).

Downgrading to critical, as the updater is currently doing the correct thing.

comment:2 Changed 10 years ago by mlinkert

  • Resolution set to fixed
  • Status changed from new to closed

Closing, as the mailing list thread suggests that this was an issue with a pre-4.4.9 daily/latest build. Feel free to re-open if anyone thinks that something can or should be done with the Apache redirects.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.64660 sec.)

We're Hiring!