I changed how check-compose upstream does email recipient config
to try and fix the 'get Atomic-related emails to Atomic people'
problem again after Fedora-Atomic composes went away. This is
an attempt to adjust the play to populate the config file for
that change. Let's see what blows up!
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The special configuration for check-compose mails for two-week
Atomic nightly composes was broken due to fedfind changes. We
need to tweak this template a bit as part of fixing it up.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
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.
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@.
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.
