Update the check-compose config file to use the variant config
for the 'Atomic' milestone as well as the 'Postrelease'
milestone - this should DTRT for the new Pungi 4 two-week
Atomic composes, which have 'Atomic' as their milestone, sending
the report to the correct addresses.
I'm switching the misc. QA fedmsg consumers over to using fedmsg-
hub, due to https://github.com/fedora-infra/fedmsg/issues/365 .
So we need to adjust how we install check-compose, install a
config file to enable the consumer, and also set up the fedmsg
base and hub roles on the openqa server boxes (which do the
check-compose job ATM).
Cloud folks want this email sent only if there's some kind of
problem (missing image or openQA failure), I've just added an
option to check-compose to allow for that, enable it here.
This is for https://phab.qadevel.cloud.fedoraproject.org/T690 ,
it goes along with some changes to check-compose itself to
allow reports for different milestones to have different config
settings, which (if I didn't mess anything up) should result in
those reports going to Mike McGrath and the cloud@ list, as
requested, while Rawhide and Branched reports continue to go to
test@ and devel@.
as per the similar recent commit to openqa roles, this is not
needed and breaks stuff (as the checkout is run during 'check'
but the install step isn't, the updated code is never installed)
I just killed the old BOS openqa deployment, which sends out
those 'compose check' emails, so I'm gonna go ahead and have
this new openqa deployment start sending out those emails a
little earlier than planned. This should result in both prod
and staging openqa running a compose check each day, but only
prod should actually send out an email report.
