apache/lucene

action failures sent to builds@lucene.apache.org

Open

#14,687 opened on May 19, 2025

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Java (879 forks)batch import
good first issuetype:enhancement

Repository metrics

Stars
 (2,179 stars)
PR merge metrics
 (Avg merge 7d 11h) (109 merged PRs in 30d)

Description

Description

Some actions that run against main, e.g. on every push, nightly release smoketest and other maintenance tasks. It would be nice if failures were sent to builds@ mailing list.

Currently the notifications are only sent to individuals? My concern is that only those individuals are seeing the issues and debugging them. If we sent the failures to the builds@ list, we could share the love.

https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/notifications-for-workflow-runs

I'm not sure if something like actions/send-email is needed for this, but it is one idea.

Contributor guide

Research direction
Investigate how to send email notifications for GitHub Actions workflow failures. The issue suggests using actions/send email or similar. Locate the workflow YAML files (e.g., for main push, nightly smoketest) and add a step to send an email to builds@lucene.apache.org on failure. Test by triggering a failure and verifying the email is sent.
Tech stack
github actions
Domain
ci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70