updates and updates-testing composes only contain Atomic images (at least at present); they kinda replace the old Fedora-Atomic composes. We directed the result mails for those composes differently (to the cloud@ list and a couple of specific relevant folks) and we should do the same for the updates and updates-testing composes, but the mechanism just isn't capable of it right now. We need to tweak the mechanism somehow to make this possible.
So this yet again turns out to be far much more effort than it feels like it ought to be, but cade6d84 and 911ffa46 should address this. They change the mechanism to allow configuration of email recipients per relevant subvariant ('relevant' subvariants being ones for which we have any test results, or for which an image was expected to be in the compose but was found to be missing). It also includes the 'email only on error' mechanism: you can specify 'send a mail to this address only if there was a test failure or missing image for this subvariant'.
I've tweaked the production deployment's config to say that the relevant folks (atomic@ , @dustymabe and @walters ) should be emailed the report if there was a test failure or missing expected Atomic image for a compose. Basically that means if a 29 nightly compose is missing one of the two expected Atomic images, or either of the openQA tests fails, they should get mailed. I hope. If I got it all right...
Metadata Update from @adamwill: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Note, can't do anything for CoreOS ATM as the CoreOS compose process is not at all connected to the way anything else is composed.
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/check-compose/issues/2
Please continue any further discussion there.