ci: bound the shared CI jobs the same way the publish job is bounded - #29
Merged
Conversation
A job no runner accepts does not fail — it waits out the 24-hour queue limit with the runner reported online and idle and no red check anywhere. That silence is the reason a broken publish pipeline went unnoticed for days in 2026-08, and nothing about it is specific to the publisher tier: any self-hosted job can become unschedulable when a host drops or a group's membership changes. So the two shared CI jobs get the same treatment the publish job just got. The bounds are generous — these finish in well under a minute — and their only job is to convert "quietly stuck" into a failure someone will see. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W9K9WE1ATSqYFStZGtLpNk
A job no runner accepts does not fail — it waits out the 24-hour queue limit with the runner reported online and idle and no red check anywhere. That silence is the reason a broken publish pipeline went unnoticed for days in 2026-08, and nothing about it is specific to the publisher tier: any self-hosted job can become unschedulable when a host drops or a group's membership changes. So the two shared CI jobs get the same treatment the publish job just got. The bounds are generous — these finish in well under a minute — and their only job is to convert "quietly stuck" into a failure someone will see. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W9K9WE1ATSqYFStZGtLpNk
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
1 participant
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.
Follow-up to #28, which bounded the publish job.
A job that no runner accepts does not fail. It sits queued until the 24-hour limit expires, with the runner reported
online/busy: falseand no annotation on the run. That silence is why a broken publish pipeline went unnoticed for days in 2026-08 — there was never a red check to look at.Nothing about that failure shape is specific to the publisher tier. Any self-hosted job becomes unschedulable when a host drops out or a group's membership changes, so the two shared CI jobs get the same bound:
plugin-ci.yml→build-testlvis-oracle-civalidate-plugin-manifest.yml→validatelvis-oracle-ciThe bounds are far above any real run; their only job is to turn "quietly stuck" into a failure someone will see. The CI group is unrestricted and has five runners, so this is defense against a rarer case than the publisher tier's — but it costs nothing and the failure mode is identical.
🤖 Generated with Claude Code
https://claude.ai/code/session_01W9K9WE1ATSqYFStZGtLpNk