Improve method to obtain current development release for ISO list generation

Bug #553616 reported by Andres Rodriguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TestDrive
Fix Released
High
Andres Rodriguez
testdrive (Ubuntu)
Fix Released
High
Andres Rodriguez

Bug Description

The method to obtain the current development release should be improved to automatically obtain it, so that the user nor the maintainer wouldn't have to do the change every time there's a new development release.

The approach for the current release will be as proposed by the maintainer:

1. wget from cdimage the code name
2. Cache the code name of the "development" release, (i.e. /var/cache/testdrive/ubuntu-development), for amount of time.
3. update cache when expired (daily?)
4. Figure out any other way to obtain this information.
5. Set the code name in the config file from the cache

For Testdrive Modularization:

This would be merged in the modularization in a way that will work for any Front-end, because this code will allow us to create the ISO list that will be needed to create the list of items in the interface for Testdrive-GTK.

Related branches

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Btw... I cannot change the status and importance of the bug :).

Changed in testdrive:
assignee: nobody → Dustin Kirkland (kirkland)
status: New → Confirmed
Changed in testdrive:
status: Confirmed → Triaged
importance: Undecided → High
Changed in testdrive (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Dustin Kirkland (kirkland)
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Hey pitti-

Question for you...

In testdrive's /etc/testdriverc file, there's a line that sets the target release code, for what is to be testdriven:

$ grep -n "r = .*lucid" /etc/testdriverc
60:r = "lucid"

After Lucid releases, and cdimage starts building whatever lucid+1 images are called, I'd like to bump this value in the conffile, such that people can use Lucid to testdrive Lucid+1.

Can I get this SRU'd easily enough? Or would it be better to build in logic like:
  wget -q -O- http://cdimage.ubuntu.com/daily/current/source/MD5SUMS | awk -F"[^0-9a-zA-Z ]" '{print $2}'

This is "smarter" in that it can figure out the new release, but that's a lot of network calls...

Or, better yet, do we have a "fast" way in python to query what the current development release's code name is?

Changed in testdrive:
status: Triaged → In Progress
assignee: Dustin Kirkland (kirkland) → Andres Rodriguez (andreserl)
Changed in testdrive (Ubuntu):
status: Triaged → In Progress
assignee: Dustin Kirkland (kirkland) → Andres Rodriguez (andreserl)
Changed in testdrive (Ubuntu):
status: In Progress → Fix Committed
Changed in testdrive:
status: In Progress → Fix Committed
assignee: Andres Rodriguez (andreserl) → Dustin Kirkland (kirkland)
Changed in testdrive (Ubuntu):
assignee: Andres Rodriguez (andreserl) → Dustin Kirkland (kirkland)
Changed in testdrive:
status: Fix Committed → In Progress
Changed in testdrive (Ubuntu):
status: Fix Committed → In Progress
Changed in testdrive:
assignee: Dustin Kirkland (kirkland) → andresrleong (andresrleong)
assignee: andresrleong (andresrleong) → Andres Rodriguez (andreserl)
Changed in testdrive (Ubuntu):
assignee: Dustin Kirkland (kirkland) → Andres Rodriguez (andreserl)
Changed in testdrive (Ubuntu):
milestone: none → later
Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 553616] Re: Improve method to obtain current development release for ISO list generation

Hello Dustin,

Dustin Kirkland [2010-04-02 4:49 -0000]:
> In testdrive's /etc/testdriverc file, there's a line that sets the
> target release code, for what is to be testdriven:
>
> $ grep -n "r = .*lucid" /etc/testdriverc
> 60:r = "lucid"

Indeed it might be better to not hardcode this at all.

> After Lucid releases, and cdimage starts building whatever lucid+1
> images are called, I'd like to bump this value in the conffile, such
> that people can use Lucid to testdrive Lucid+1.
>
> Can I get this SRU'd easily enough?

Yes, if you want to keep the hardcoding for lucid, this makes a
trivial SRU. In fact, we already know the next release name, so
perhaps you could even upload that into lucid proper.

> Or would it be better to build in logic like:
> wget -q -O- http://cdimage.ubuntu.com/daily/current/source/MD5SUMS | awk -F"[^0-9a-zA-Z ]" '{print $2}'

I wouldn't use cdimage, but either query launchpad (with launchpadlib,
if you use that anyway, or grep https://launchpad.net/ubuntu/+series),
or query archive.ubuntu.com (Michael Vogt would know what to check
for). Compared to the image rsyncing that testdrive has to do
anyway, this extra HTTP call sounds negligible?

Do you provide a CLI argument/GUI option to override the "current
devel release"? Folks might also want to testdrive an LTS point
release, etc.

Thanks,

Martin

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package testdrive - 1.38-0ubuntu1

---------------
testdrive (1.38-0ubuntu1) lucid; urgency=low

  * testdrive: support usb-creator-kde, LP: #570509

testdrive (1.37-0ubuntu1) lucid; urgency=low

  [ Andres Rodriguez ]
  * debian/control, testdrive, testdriverc: update the testdrive cache
    at most once per week on launch, dynamically determine Ubuntu
    development release and cache it, LP: #570485, #553616

  [ Dustin Kirkland ]
  * debian/control: recommend usb-creator for gtk or kde
 -- Dustin Kirkland <email address hidden> Mon, 26 Apr 2010 21:14:21 -0500

Changed in testdrive (Ubuntu):
status: In Progress → Fix Released
Changed in testdrive:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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