Repository navigation
Allow explicit local backends in hosted dev builds #13129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
inputs.refselects a revision withoutscripts/lib/dev-backend-origin.sh, this step succeeds without validating the backend selection. The tagged build then continues through setup beforereload.shfails while sourcing the missing helper, so the intended early validation becomes a later failure with less useful guidance. Require the helper or report an actionable error in this step.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The conditional preserves builds of historical source refs. I checked the parent of the commit that introduced this helper: reload.sh at e42dc540df directly uses its local dev origin and never sources
dev-backend-origin.sh. Its absence therefore does not cause the later missing-helper failure described here. The remote-URL presence check is unconditional; revisions that implement the backend resolver additionally run its URL/mode validation. Requiring that newer helper for every historical ref would reject otherwise buildable legacy sources. Keeping this compatibility path; no source change for this finding.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You’re right. The historical
reload.shate42dc540dfdoes not sourcedev-backend-origin.sh, so its absence cannot cause the later failure described in the comment. The unconditional remote-URL guard still enforces the new hosted-runner policy, while resolver validation is correctly limited to refs that contain the helper. I’m withdrawing this finding; no source change is needed.