Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Test Data
-
Labels:None
-
Story Points:7.5
-
Epic Link:
-
Team:SQuaRE
Description
The email plugin was installed and configured to send out email notifications after a build. This was setup for the ts_xml and ts_sal jobs. Emails stopped working a couple of months ago. The build logs show they are sent, but the recipients never get the messages. I asked IT, as I thought the spam filter might be catching them, but they confirmed that no traffic from Jenkins is being blocked. My next thought is that the messages are being blocked at the source, AWS. Since this is not an area I can access, I am filing a ticket.
Last week I was able to demonstrate working email notifications in a test env using aws ses for delivery. It appeared that the extra features of the jenkins email-ext and emailext-template plugins weren't being used and that the more basic mailer plugin would be sufficient. email-ext requires duplicate configuration with mailer, which it also depends on,and doesn't provider a "test" feature either. I suspect this duplicate configuration has contributed to the email problems in the past.
The configuration of aws-ses has been terraform-erized and a PR is open to update the jenkins deployment to fully configure the mailer plugin, remove the unneeded mail related plugins, and change the github oauth scopes to allow user email addresses to be retrieved. I prefer to do a restart when an auth change is made to ensure there aren't any lurking issues with cached metadata and a maintenance period needs to be scheduled to roll out these changes.