[yast-devel] Jenkins mailing someone wrong about build failures
Hello, while checking the admin@o.o tickets, I found one that says the YaST Jenkins instance mails someone who should not receive those mails: === It looks like for some reason your Jenkins thinks commits made via github are associated with this email address so I keep getting notifications when builds fail. This has been happening for a few months now. === See https://progress.opensuse.org/issues/14450 for details, and feel free to respond there directly. Also note that the ticket was bitrotting for 3 months, so if you already accidently ;-) fixed this in the meantime, just say so ;-) Regards, Christian Boltz -- A bug is a test case you haven't written yet. [http://www.diveintopython.net/refactoring/index.html] -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Sun, 15 Jan 2017 22:30:45 +0100 Christian Boltz <opensuse@cboltz.de> wrote:
Hello,
while checking the admin@o.o tickets, I found one that says the YaST Jenkins instance mails someone who should not receive those mails:
=== It looks like for some reason your Jenkins thinks commits made via github are associated with this email address so I keep getting notifications when builds fail. This has been happening for a few months now. ===
See https://progress.opensuse.org/issues/14450 for details, and feel free to respond there directly. Also note that the ticket was bitrotting for 3 months, so if you already accidently ;-) fixed this in the meantime, just say so ;-)
Regards,
Christian Boltz
Hi Christian, we already explained it via email. Root of issue is somewhere in jenkins. When git repo is edited via github web access it have that change is done via github and jenkins think it is done by user github and for whatever reason it is associated with given mailing address github@ . So it should be fixed in jenkins itself. It have nothing to do with our setup, as we use simple send email in case of failure to authors of commits that broke it. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hello, Am Montag, 16. Januar 2017, 09:41:14 CET schrieb Josef Reidinger:
we already explained it via email. Root of issue is somewhere in jenkins. When git repo is edited via github web access it have that change is done via github and jenkins think it is done by user github and for whatever reason it is associated with given mailing address github@ . So it should be fixed in jenkins itself. It have nothing to do with our setup, as we use simple send email in case of failure to authors of commits that broke it.
So what is the solution until Jenkins gets fixed upstream? Annoy that poor soul with Jenkins reports? ;-) If everything else fails, block or redirect those mails in Postfix. I'd guess a virtual_alias_maps file with github@example.com jreidinger@suse.cz # replace example.com with the correct domain of course, I just # don't want to expose it for spammers ;-) should do the job. (Of course this Postfix instance should only be used by Jenkins to avoid that unrelated mails get redirected.) Regards, Christian Boltz -- [Virenscanner] Stattdessen gehört auf einen Windows-Arbeitsplatz ein guter, selbstaktualisierender lokaler Scanner, der die Windows-Kiste so richtig schön langsam beim Öffnen von Dateien macht, um den Windows-Anwender zu motivieren, auf Linux umzusteigen. [Kristian Koehntopp in suse-linux] -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Christian Boltz -
Josef Reidinger