Hi Chris,
Our dev list is pretty low traffic overall, a dozen or so emails a month. So
even though Jenkins build failures are a lot of that, I don't think they are
distracting, at least not for me.
Back in January I see there were more. I think that was uncommon though.
If anyone else on the list thinks we should make some adjustments, do feel free
to speak up. My own email management isn't necessarily the same as how everyone
does it :)
Thanks Chris for the input
-Dave
On 3/15/24 7:46 AM, Christofer Dutz wrote:
Hi all,
while reviewing your projects activities as part of my preparation for next
week's board meeting, I came across the fact that the one entity responsible
for almost 50% of your dev-lists traffic, is build failure notices from Jenkins.
I also left a comment on your last board report about this.
Generally I'm a big fan of having build failure notifications on dev@, however
I guess this only applies to build failures on the main branch. From me it
looks as if here for every pr, issue, whatsoever all messages are delivered
here.
I would consider that harmful. The dev list should be a place where the project
discusses matters of the project and is not flooded by such notifications.
Perhaps an approach that other projects are using might be something the
project could consider? Many other projects use GitHub Actions for the building
of PRs etc. and only use Jenkins for special tests that require special agents
or for staging and deploying websites and artifacts.
The good thing here is that when using GitHub Actions, only the people involved
in a PR get direct feedback emails and the rest of the project is not disturbed.
I hope this sort of feedback is welcome, if not, give me a notice and I'll try
to remember that for the next time.
Also please add me in CC for any responses, as I'm not subscribed here.
Chris
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
