Repository navigation
Conversation
whi-tw
force-pushed
the
observe-workflow-failures
branch
3 times, most recently
from
October 20, 2026 13:16
93f7d8a to
95d9960
Compare
whi-tw
force-pushed
the
observe-workflow-failures
branch
from
October 20, 2026 13:29
95d9960 to
e9e6402
Compare
There is no view of how often CI fails or slows down over time, so this runs a weekly summary by calling the shared workflow in forms-deploy. It is a dry run for now: the digest goes to the job summary, not Slack.
Without a timeout a hung job runs for six hours. The limits are well above normal run times and only exist to catch hangs.
whi-tw
force-pushed
the
observe-workflow-failures
branch
from
October 29, 2026 13:38
e9e6402 to
4533486
Compare
Contributor
|
🎉 A review copy of this PR has been deployed! It is made of up two components It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready For the sign in details and more information, see the review apps wiki page. |
This branch has not been deployed
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.
What problem does this pull request solve?
Trello card: https://trello.com/c/jPeqHHPu/772-improve-the-observability-of-our-github-workflows
There is no view of how often CI fails or slows down over time. This adds a weekly "CI digest" workflow: how often this repo's workflows failed in the last week compared with the previous 12 weeks, which jobs and specs failed, and how long runs take. It calls the shared workflow added in govuk-forms/forms-deploy#2365, where the digest is described in full.
It is a dry run for now. Each run writes the digest to its job summary and nothing is posted to Slack until we have seen a few weeks of output. Going live is a one-line change in forms-deploy, with nothing to change here.
It also sets
timeout-minuteson every job that runs on a runner, so a hung job fails fast instead of running for up to six hours. The limits are generous and well above the observed run times, so they only catch hangs. Jobs that only call a reusable workflow cannot set one; their limits come from forms-deploy. Once govuk-forms/forms-deploy#2332 merges, the shared workflow lint fails any job that has none.Earlier commits on this branch called the shared workflows from a forms-deploy branch, and those runs passed; they can be found in this branch's Actions history. The digest only runs from the default branch, so its first run in Actions will be after merge.
Before merging
Posting to Slack needs the org secret
SLACK_WEBHOOK_GOVUK_FORMS_DEPLOYMENTSto be available to this repo. That is only needed once the digest goes live, not to merge this.Things to consider when reviewing