snapshots "latest" target for ubuntu cannot be used

Bug #1270247 reported by Mike Holmes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro CI
Triaged
Wishlist
Unassigned

Bug Description

If a LAVA job has no need to be concerned which version it is running, such as for many ssh hacking sessions, or general running of tests when developing them, it is convenient to have a canned JASON file that may be pasted into the web submit job link without editing it every day.

This works for the kernel, where latest has a stable target file name every day.
https://snapshots.linaro.org/kernel-hwpack/linux-lng-le-preempt-rt-arndale/latest/arndale-lng-sd.img.gz

However for the rootfs it cannot be done, because the target encodes the date and build number into the file name.
http://snapshots.linaro.org/ubuntu/images/developer/latest/linaro-saucy-developer-20140115-620.tar.gz

Can the ubuntu image have a link added that has a stable name ?
http://snapshots.linaro.org/ubuntu/images/developer/latest/linaro-saucy-developer.tar.gz --------> http://snapshots.linaro.org/ubuntu/images/developer/latest/linaro-saucy-developer-20140115-620.tar.gz

Revision history for this message
Tyler Baker (tyler-baker) wrote :

This is a CI request not specific to LAVA.

affects: lava-server → linaro-ci
Revision history for this message
Milosz Wasilewski (mwasilew) wrote :

+1

Fathi Boudra (fboudra)
Changed in linaro-ci:
assignee: nobody → Fathi Boudra (fboudra)
importance: Undecided → Wishlist
Fathi Boudra (fboudra)
Changed in linaro-ci:
assignee: Fathi Boudra (fboudra) → nobody
status: New → Triaged
Revision history for this message
Fathi Boudra (fboudra) wrote :

FWIW, why bother to use moving target when all you want is an image to boot on? Isn't it better to use a released image instead?

Revision history for this message
Mike Holmes (mike-holmes) wrote : Re: [Bug 1270247] Re: snapshots "latest" target for ubuntu cannot be used

One reason is because you get set up testing something, have to put it to
once side and then comeback to it after say some blocker is moved by which
time the links are dead.
Another is in wikis where you want to post up ways to get things done as
examples and they quickly date - i.e. within 24 hours.
Lastly it is a really great way to just establish sanity on something
without looking for a version number to put in there, for example it you
want to check if something is fixed yet upstream.

Mike

On 22 January 2014 09:15, Fathi Boudra <email address hidden> wrote:

> FWIW, why bother to use moving target when all you want is an image to
> boot on? Isn't it better to use a released image instead?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1270247
>
> Title:
> snapshots "latest" target for ubuntu cannot be used
>
> Status in Linaro Continuous Integration:
> Triaged
>
> Bug description:
> If a LAVA job has no need to be concerned which version it is running,
> such as for many ssh hacking sessions, or general running of tests
> when developing them, it is convenient to have a canned JASON file
> that may be pasted into the web submit job link without editing it
> every day.
>
> This works for the kernel, where latest has a stable target file name
> every day.
>
> https://snapshots.linaro.org/kernel-hwpack/linux-lng-le-preempt-rt-arndale/latest/arndale-lng-sd.img.gz
>
> However for the rootfs it cannot be done, because the target encodes the
> date and build number into the file name.
>
> http://snapshots.linaro.org/ubuntu/images/developer/latest/linaro-saucy-developer-20140115-620.tar.gz
>
> Can the ubuntu image have a link added that has a stable name ?
>
> http://snapshots.linaro.org/ubuntu/images/developer/latest/linaro-saucy-developer.tar.gz -------->
> http://snapshots.linaro.org/ubuntu/images/developer/latest/linaro-saucy-developer-20140115-620.tar.gz
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-ci/+bug/1270247/+subscriptions
>

Revision history for this message
Chase Qi (chase-qi) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.