#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 dcantrel):
Solving this problem was/is a goal of the anaconda CI project. Composes
happen when code is checked in, test cases run, and we see the build
output on a web page. There are problems:
1) We need more test cases and no one wants to write them. This is a
large part of the ongoing "WE NEED BETTER TESTING" issue that is regularly
discussed. Perhaps we should do an activity day or two where a bunch of
us get together, decide on test cases, and bang them out. Maintenance of
test cases is easier than coming up with them from scratch.
2) rawhide is always broken. This makes #1 seem less pressing. We have
the ability to trigger builds of packages as we check in code and tree
composes of those new packages, but the other packages come in from
rawhide, naturally. But the rate of change there means nothing is ever
usable for long enough. It's not until we get to the test composes for
the next Fedora release that we start to see moderately usable repos.
Maybe this doesn't matter. Maybe we change the expectation to say that,
yes, we do trigger builds and stuff automatically, but as long as the tree
compose that is triggered is broken AND we don't own the broken component,
we don't care. Except, when we branch we should start caring about those
automatically triggered composes.
3) If we can sort out #3, what I really really want to happen is to gate
commits to pkgdb based on the outcome of the automated test runs. Both
the test runs and builds of the package itself (e.g., anaconda) and the
test runs of the test compose built with that new package. We should have
a minimal set of cases that pass BEFORE we commit to pkgdb and drop it in
to real Fedora. But again, we need to solve #1 and #2.
The infrastructure to do this is there. We even have hardware. And I
bought more hardware too.
I'm interested in talking about this more and converging our ideas
somehow. Because I think we're talking about overlapping things that are
mutually beneficial.
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/6383#comment:3>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project