Repository navigation
[OPENJPA-3015] Mail the dev list when a workflow run fails - #214
Merged
Merged
Conversation
The scheduled Databases workflow runs weekly and a failure went unnoticed until someone happened to look. The jobs notification scheme mails a run that fails, and one that succeeds after a series of failures; successful runs are not mailed.
solomax
approved these changes
Oct 13, 2026
cristof
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Following @solomax request on #209: the weekly
Databasesworkflow failed on its first scheduled run and nobody was told..asf.yamlgrows anotifications.jobstarget. Per the infrastructure documentation this "triggers emails when a workflow run fails or if it succeeds after a series of failures", and normal successful runs are not mailed, so the volume stays low.Two notes: the scheme only takes effect in the default branch, so it starts working once this is merged, and each change to the notification settings is announced to
private@. I useddev@openjpa.apache.orgso the failures are visible to everyone working on the code — say the word if you would rather have them oncommits@.The failures from that first run are tracked separately in OPENJPA-3016 (criteria tests failing on MariaDB and then exhausting the connection pool;
TestPessimisticLockson PostgreSQL).