#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 clumens):
Replying to [comment:11 tflink]:
Is there any documentation on how anaconda's system works? I
understand
the jenkins+lorax part but I'm still fuzzy on how that's kicked
off -
monitoring a git repo (github? rh internal?), by hand, something else I'm
not thinking of?
There's not great documentation, no. We have testing at several levels.
We have a lot of stuff in anaconda/tests/ that gets run in jenkins that is
kicked off by monitoring the github repo. We additionally have those same
tests run in response to github pull requests (but only ones from the
anaconda team - don't want to run arbitrary people's arbitrary code).
Additionally, there's the kickstart-tests which are also in github. Those
are kicked off nightly, following a build of a boot.iso. That boot.iso
contains scratch builds of the latest things from anaconda, pykickstart,
and blivet git.
I try to push as much of the details of how it all works into source
control and leave the jenkins bit be boring scheduling and RPM scp'ing
work.
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/6383#comment:13>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project