fix(hardware): support cross-origin builds in revision selectors - #2051
Merged
alanpeixinho merged 1 commit intoAug 20, 2026
Merged
Conversation
Closes kernelci#2047 Signed-off-by: Alan Peixinho <alan.peixinho@profusion.mobi>
felipebergamin
approved these changes
Aug 19, 2026
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 it is
Hardware revision selectors filtered by
builds.origin, so origins liketi(tests on other origins' builds) got an empty tree/branch/revision list.For those cross-origin test origins, selectors now drive from
tests(last 30 days, platform set) so only revisions that actually have tests for that origin appear. Other origins keep the builds-based path.Closes #2047
How to test
/hardware?o=ti— Tree / Branch / Revision selectors should appear and be non-empty./hardware(maestro) — selectors still work as before.