Raise publish build timeout to 10 minutes#340
Merged
corporate-gadfly merged 1 commit intoJun 17, 2026
Conversation
The publish `build` job is capped at `timeout-minutes: 5`, but the build was already running ~4m41s (references:all clones and generates docs for three products, which is network-variable). The component-version refresh tasks added in OpenVoxProject#339 make additional live GitHub API calls, pushing a representative build to ~5m06s — over the cap — so the job was cancelled at the Archive step and the deploy was skipped, leaving master unpublished. Raise the cap to 10 minutes to restore publishing and give headroom for the network-variable build. Signed-off-by: Michael Harp <mike@mikeharp.com> Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
2 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.
What
Raise the publish
buildjob'stimeout-minutesfrom 5 to 10.Why
The merge of #339 left
masterunpublished: its publish run was cancelled at the Archive website step anddeploywas skipped. Root cause is the 5-minutebuildtimeout, not a build error:buildjob durationreferences:allclones and generates docs for three products (network-variable), and the component-version refresh tasks added in #339 make additional live GitHub API calls. The build was already at the edge of the 5-minute cap; the extra calls tipped it over. "Build website" itself succeeds — it's purely cumulative time, so more headroom is the fix.