#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 tflink):
In terms of what's possible, we can get anaconda commits as fedmsg using
[
https://apps.fedoraproject.org/github2fedmsg/ github2fedmsg]. Once we
have those fedmsgs, we can run taskotron tasks in response. The same thing
can be said about koji builds or dist-git changes (using the dist-git
features for taskotron currently in alpha). Any of the options for
building test content (local lorax, local pungi, releng) can be made to
work and some are easier/saner than others.
In short, I don't see anything which would prevent Taskotron from running
the bits being discussed here.
In terms of what to run and where to run those tests, I'm still a bit hazy
on the details. Is the desire to run the same things that anaconda's CI
runs in not-anaconda-specific systems, get results into a place where they
can be used for gating decisions or are we looking to reduce the number of
systems running tests?
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/6383#comment:14>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project