I'm with Swapnil on this one. I think the way we make it less noisy is to take the time to fix the failing tests.
I suppose we could split the difference and give the CI emails a, say, daily cadence. No news is good news, or else it gives you all the failures in the last 24 hours. Don't know how easy that would be to cache and report under the existing framework, though. On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett <jbarr...@pivotal.io> wrote: > It’s sad that the most frequent spammer... errrr... I mean mailer is the > new CI process. If we aren’t going to send it elsewhere how can we make it > less noisy? > > -Jake > > > > On Mar 20, 2018, at 8:37 PM, Dan Smith <dsm...@pivotal.io> wrote: > > > > I was curious about the stats for bot vs. humans on the dev list. Out of > > 915 messages, looks like we're about 50% robot. > > > > I'm still be in favor of not sending these messages to dev@geode. Long > time > > members have probably already created a mail filter by now (I know I > have) > > so we're only hurting newbies by sending a bunch of messages. > > > > 1) apac...@gmail.com 241 > > 2) Spring CI 109 > > 3) Kirk Lund 63 > > 4) Apache Jenkins Server 51 > > 5) Anthony Baker 41 > > 6) Dan Smith 40 > > 7) Travis CI 38 >
