#6383: Build a 'test' compose automatically when installer-related packages
change
-----------------------+-----------------------
Reporter: adamwill | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: other
Resolution: | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Comment (by adamwill):
yeah, there are definitely obvious overlaps. I'd say right now we have
testing at two fairly different levels: you're testing down at the level
of individual anaconda commits, we (QA) are testing way up at the level of
entire nightly distribution composes. That's as important a difference as
the difference between anaconda's kickstart-based test mechanism and
openQA's completely different mechanism.
This would be another level again which kind of comes between the two - I
wasn't envisaging doing this level of testing on every anaconda commit, or
even every anaconda tag or package build, it seems like too heavy a
process for that. I was envisioning doing it at the level of updates.
(This also avoids the problem of knowing when we need to pull in an
updated blivet or pyparted or whatever along with the updated anaconda,
because the update should include all necessary packages and if it doesn't
that's an error).
I think there's value in having these different levels of tests and also
in having different test mechanisms - there are things openQA-style
testing can catch that kickstart testing just can't, and there are things
that are way more unwieldy to test openQA-style than kickstart-style. But
we should definitely avoid duplication between them as far as possible. So
yeah, ideally we definitely shouldn't have different test processes each
with their own image building mechanism, we should have a single image
building mechanism which produces the images needed for each level of
testing.
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/6383#comment:4>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project