Repository navigation
ci(release): list failed jobs in pre-release failure notices - #4719
Merged
matthewgrossman merged 2 commits intoOct 19, 2026
Merged
Conversation
…ilure notices The pre-release failure notification said only that the run failed. Name the failed stage (build, publication, or release qualification), link the tag, and list each failing job of the run attempt with a link. Skip the aggregate Release Qualification job unless it is the only failure, and still send the message if the jobs lookup fails. Closes #4718 Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
matthewgrossman
requested review from
a team,
derekwaynecarr,
mrunalp and
sjenning
as code owners
October 19, 2026 16:49
|
🌿 Preview your docs: https://nvidia-preview-pr-4719.docs.buildwithfern.com/openshell |
Drop the stage headline and the aggregate-job filtering. Keep the existing message and append a link to each failed job. Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
matthewgrossman
changed the title
SDAChess
approved these changes
Oct 19, 2026
matthewgrossman
enabled auto-merge
October 19, 2026 17:05
matthewgrossman
deleted the
ci/4718-prerelease-failure-notice/matthewgrossman
branch
October 19, 2026 17:21
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
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.
Summary
List the failed jobs, with links, in the pre-release failure Slack notification, so triage doesn't have to search a 90-job run for the problem. Drew suggested this in the triage thread for
v0.1.5-pre.5.Related Issue
Closes #4718
Changes
failureortimed_outjob in the current run attempt. The list comes from the Actions jobs API, so the job now hasactions: read.CI.mdmentions the job links.For
v0.1.5-pre.5(run 39250333833), the message would be:Testing
Extracted the step script and ran it locally, with
curlreplaced byjq, against the real jobs of run 39250333833 and with a failed jobs lookup.actionlintandshellcheckpass on the changed step.I couldn't send a real Slack message from a branch. The first failed pre-release after merge will confirm it.
Checks appropriate to the affected code and behavior pass
Unit tests added/updated (if applicable)
E2E tests added/updated (if applicable)
Checklist