use variables for release numbers in upgrade tests
ClosedPublic

Authored by adamwill on Dec 18 2015, 3:46 PM.

Details

Summary

Along with the matching change to fedora-openqa-schedule to pass
these variables in when scheduling jobs, this avoids hardcoding
the release numbers for the upgrade tests (which means someone
has to remember to edit them every release). The new createhdds
similarly uses get_current_release() to decide what releases it
needs images for, so all this should hook up and work magically
without any human intervention required.

For clarity, the effect of the '_upgrade_' tests is "run an
upgrade from the 'current' Fedora release to whatever release
is being tested", and the effect of the '_upgrade_2_' tests is
"run an upgrade from the 'previous' Fedora release to whatever
release is being tested".

Test Plan

Apply with D702, schedule upgrade tests, and make
sure the correct hard disk image filenames are used.

Diff Detail

Repository
rOPENQATESTS os-autoinst-distri-fedora
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to use variables for release numbers in upgrade tests.Dec 18 2015, 3:46 PM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jskladan, garretraziel.
garretraziel accepted this revision.Dec 22 2015, 7:42 AM

Sure, looks OK.

This revision is now accepted and ready to land.Dec 22 2015, 7:42 AM
This revision was automatically updated to reflect the committed changes.