Google automatically disables the password we use to send emails on CI failure if it isn’t used regularly – so if CI stays green for a few months, then we don’t get notified once it breaks because the email sending will also be broken. To avoid this, let’s just send regular emails (weekly?) using the same credentials, also from GitHub actions, but to some other recipient email address that nobody looks at. This way, the password should stay active from Google’s perspective.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T353960 EntitySchema daily CI broken and emails broken | |||
Resolved | ItamarWMDE | T365704 [SW] Send regular emails from EntitySchema daily CI to burner address |
Event Timeline
Change #1037671 had a related patch set uploaded (by Arthur taylor; author: Arthur taylor):
[mediawiki/extensions/EntitySchema@master] Add weekly keepalive / heathcheck mail for secondary CI
Change #1037671 merged by jenkins-bot:
[mediawiki/extensions/EntitySchema@master] Add weekly keepalive / heathcheck mail for secondary CI
Change #1042250 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/EntitySchema@master] Fix GitHub Actions syntax
Not quite, but that was enough to make me compare it to the other file and spot the issue ^^
(It’s not actually an error in the YAML syntax, it just doesn’t follow the structure that GitHub expects.)
Change #1042250 merged by jenkins-bot:
[mediawiki/extensions/EntitySchema@master] Fix GitHub Actions syntax
Looks like it’s not working:
Error: Invalid login: 534-5.7.9 Application-specific password required. For more information, go to 534 5.7.9 https://support.google.com/mail/?p=InvalidSecondFactor d2e1a72fcca58-705ccb72555sm6891649b3a.181 - gsmtp
I believe @WMDE-leszek fixed the password, so next Monday we can check again whether this worked.