maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: Buildbot MariaDB->MariaDB upgrade testing
CREATION DATE..: Wed, 12 May 2010, 13:48
SUPERVISOR.....: Knielsen
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Other
TASK ID........: 118 (http://askmonty.org/worklog/?tid=118)
VERSION........: Server-9.x
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 5
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 8

PROGRESS NOTES:

-=-=(Knielsen - Fri, 14 May 2010, 06:40)=-=-
Installed the new virtual images, using 5.1.42 from OurDelta (for all except
lucid, which is new and so has no 5.1.42 ourdelta package and also needed a
fixed set of packages due to changes in the lucid MySQL packaging).

Added a new upgrade2 step in the Buildbot configuration to test this.

Updated Buildbot wiki documentation.
Worked 5 hours and estimate 0 hours remain (original estimate decreased by 3 hours).



DESCRIPTION:

Create an additional test step for Buildbot to check that upgrading from one
version of MariaDB to another works ok.

We already have testing of upgrade from distro-official MySQL .debs to
our MariaDB .debs.

What we need is for each Debian/Ubuntu, a new KVM virtual image with MariaDB
5.1.42 (First GA release) pre-installed, just like the existing update test
uses images with MySQL pre-installed.

Then the Buildbot configuration must be updated to add another upgrade test
step, just like the existing one but using the images with MariaDB pre-installed.

Also, the setup of the new images must be added to the existing documentation:

    http://askmonty.org/wiki/BuildBot::package
    http://askmonty.org/wiki/BuildBot:vm-setup


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)