Infrastructure

As discussed yesterday on freenode #libreoffice-dev:

Apr 17 14:47:50 <samuel_m>    sberg: and I added an email notification step to https://ci.libreoffice.org/job/lo_tb_master_linux_dbg/ so that "notification e-mail will be sent to individuals who have committed changes for the broken build", see https://wiki.jenkins.io/display/JENKINS/Mailer
Apr 17 14:51:14 <sberg>    samuel_m, cloph, any reason to enable that mail notification only for that one job?
Apr 17 14:51:38 <samuel_m>    sberg: can you identify a list of jobs where that would make sense too?
Apr 17 14:51:53 <samuel_m>    I can add it then, but I don't know the purpose of most jobs
Apr 17 14:52:02 <sberg>    samuel_m, I don't care, as I'm subscribed to that mailing list anyway :)
Apr 17 14:57:17 <samuel_m>    cloph, sberg: maybe all of those "Tinderbox on Master for x" 
Apr 17 15:00:09 <samuel_m>    done it now
Apr 17 15:00:27 <samuel_m>    so if you get spammed by Jenkins, it's my fault :)
Apr 17 15:00:57 <samuel_m>    although I configured it to send only one mail when the build fails (even if all following builds fail, no further mail will be sent)

That means that, in addition to "Failure/Still Failing/Fixed!" emails sent to the <libreoffice-ci@global.libreoffice.org> mailing list, similar (but differently worded) "Build failed in Jenkins/Jenkins build is back to normal" emails are also sent to individual committers.

However, I observe that since the above change, the "Failure/Still Failing/Fixed!" emails sent to the <libreoffice-ci@global.libreoffice.org> mailing list often are no longer properly threaded. For example, the two emails

Date: Wed, 17 Apr 2019 21:41:51 +0000 (UTC)
From: ci@libreoffice.org
To: libreoffice-ci@global.libreoffice.org
Message-ID: <1907370684.265.1555537311847.JavaMail.ci@vm145.documentfoundation.org>
Subject: [global-libreoffice-ci] Tinderbox on Master for Windows - Build # 21609 - Failure!

(archived at <https://listarchives.libreoffice.org/global/libreoffice-ci/msg26109.html> "[global-libreoffice-ci] Tinderbox on Master for Windows - Build # 21609 - Failure!") and

Date: Wed, 17 Apr 2019 21:55:20 +0000 (UTC)
From: ci@libreoffice.org
To: libreoffice-ci@global.libreoffice.org
Message-ID: <848999827.268.1555538120823.JavaMail.ci@vm145.documentfoundation.org>
In-Reply-To: <1340270904.263.1555537311454.JavaMail.ci@vm145.documentfoundation.org>
References: <1340270904.263.1555537311454.JavaMail.ci@vm145.documentfoundation.org>
Subject: [global-libreoffice-ci] Tinderbox on Master for Windows - Build # 21610 - Fixed!

(archived at <https://listarchives.libreoffice.org/global/libreoffice-ci/msg26110.html> "[global-libreoffice-ci] Tinderbox on Master for Windows - Build # 21610 - Fixed!") should form a thread, via the second one's In-Reply-To referencing the first one's Message-ID, but that is not the case.

(<https://listarchives.libreoffice.org/global/libreoffice-ci/> unfortunately doesn't expose the raw email headers, but if you look at <https://listarchives.libreoffice.org/global/libreoffice-ci/threads.html&gt;, then emails with dates up to ca. "Wed Apr 17 13:19:17 GMT 2019" are shown properly threaded, while many of the emails with dates since ca. "Wed Apr 17 14:18:55 GMT 2019" are not.

I am subscribed to the <libreoffice-ci@global.libreoffice.org> mailing list, and the missing threading is a pain for me---esp. so given the high email volume on that list.