Repository navigation
Open an issue when a scheduled bump workflow fails - #7312
Merged
Merged
Conversation
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
janniklasrose
approved these changes
Nov 3, 2026
Member
|
same for bump go toolchain? |
Co-authored-by: Isaac <no-reply@databricks.com>
Move the Report failure step into a composite action and use it from both scheduled bump workflows. Co-authored-by: Isaac <no-reply@databricks.com>
pietern
changed the title
pietern
commented
Nov 3, 2026
pietern
left a comment
pietern
left a comment
Contributor
Author
There was a problem hiding this comment.
@janniklasrose Good suggestion, done!
A team mention posted by github-actions did not notify the team's members. Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
pietern
enabled auto-merge
November 3, 2026 13:33
Collaborator
Integration test reportCommit: c56b0a0
Top 6 slowest tests (at least 2 minutes):
|
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.
The scheduled
Bump vulnerable dependenciesworkflow failed every day from Oct 9 to Oct 15 (JFrog returned 403 forgolang.org/x/net@v0.60.0, then a transientactions/setup-godownload failure), and nobody noticed because a failed scheduled run is only visible in the Actions tab. The fix for the Oct 8x/netadvisories landed in #7083 on Oct 16 as a result.Bump Go toolchainhas the same blind spot.This adds a composite action,
.github/actions/report-failure, and runs it as the last step of both workflows withif: failure(). It opens an issue that links the failed run and is assigned to the same people each workflow already requests as PR reviewers. The assignee list lives in each workflow next to itsreviewers:list so the two are easy to keep in sync. If an open issue with the workflow's label (bump-vuln-deps-failureorbump-go-toolchain-failure) already exists, it comments on it instead, so a multi-day outage produces a single issue. The label is created on first use. Both jobs gainissues: writefor this.The issue body also mentions
@databricks/eng-deco-cli, but a team mention posted bygithub-actionsdid not notify team members in testing, which is why the issue is assigned to individuals.Tested by temporarily forcing the vulnerable-dependency workflow to fail on this branch and dispatching it. The first run, with an earlier inline version that only had the team mention, created #7311 but sent no notification (run). The second run, with the final action, created #7316 with all seven assignees and delivered an assignment notification (run). Both issues were closed as tests, and the simulated failure is reverted on the branch.
This pull request and its description were written by Isaac.