I'm certainly not averse to the idea of notifications in general, but
notifications to no one are of little use. If there's someone who's
responsible for examining the failures in ceph-api-nightly or
ceph-dashboard-cephadm-e2e-nightly, that person/group/alias should be
the email recipient. I'm guessing it's not ceph-qa@xxxxxxx, but I
honestly don't know who that person or group might be.
On 3/21/2023 10:47 AM, Nizamudeen A wrote:
I guess we started using this in the ceph-dashboard-cephadm-e2e-nightly
because it was there in the
ceph-api-nightly. If the mail is unused/unmonitored I guess we can
remove it from those tests.
Are there any alternative emails we should be putting there? Or do we
just go without any mail notifications?
Regards,
Nizam
On Tue, Mar 21, 2023 at 3:05 AM Dan Mick <dmick@xxxxxxxxxx
<mailto:dmick@xxxxxxxxxx>> wrote:
On 3/17/2023 7:04 PM, Dan Mick wrote:
> ceph-api-nightly and ceph-dashboard-cephadm-e2e-nightly are both
> configured to send email to ceph-qa@xxxxxxx
<mailto:ceph-qa@xxxxxxx> when the build fails, and
> again when it starts working after having failed.
>
> Is anyone monitoring that email for such notifications? Should they
> continue? Should they go somewhere less catchall, or is that
alias an
> appropriate place?
Attempt 2. If no one's using this email it's just noise and should be
removed, right?
_______________________________________________
Dev mailing list -- dev@xxxxxxx <mailto:dev@xxxxxxx>
To unsubscribe send an email to dev-leave@xxxxxxx
<mailto:dev-leave@xxxxxxx>
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx