ci: resolve staging build-deps from qli-staging - #99
Draft
Christopher Obbard (obbardc) wants to merge 1 commit into
Draft
ci: resolve staging build-deps from qli-staging#99Christopher Obbard (obbardc) wants to merge 1 commit into
Christopher Obbard (obbardc) wants to merge 1 commit into
Conversation
The build job passed a fixed 'EXTRA_BUILD_DEP_WORKSPACES: qli', so every run resolved its build-dependencies from the released qli workspace alone. Daily and PR builds are staged work: they can depend on a package version that has only reached qli-staging, and with qli the sole extra repository those builds fail to satisfy the dependency, or silently pick up the older released one. Pick the workspace list from the same input that already picks the environment and the publish path. A run that promotes to a release workspace is a Production deployment and keeps reading qli only, so a released kernel is never built against something that has not been released alongside it. A run that only builds into a CI workspace is a Staging one and reads qli and qli-staging, matching what the staged archive actually offers. Closes: #93 Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Christopher Obbard (obbardc)
temporarily deployed
to
Staging
September 3, 2026 16:21 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Christopher Obbard (obbardc)
temporarily deployed
to
Staging
September 3, 2026 16:22 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Christopher Obbard (obbardc)
temporarily deployed
to
Staging
September 3, 2026 16:24 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Christopher Obbard (obbardc)
temporarily deployed
to
Staging
September 3, 2026 16:24 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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.
The build job passed a fixed 'EXTRA_BUILD_DEP_WORKSPACES: qli', so every run resolved its build-dependencies from the released qli workspace alone. Daily and PR builds are staged work: they can depend on a package version that has only reached qli-staging, and with qli the sole extra repository those builds fail to satisfy the dependency, or silently pick up the older released one.
Pick the workspace list from the same input that already picks the environment and the publish path. A run that promotes to a release workspace is a Production deployment and keeps reading qli only, so a released kernel is never built against something that has not been released alongside it. A run that only builds into a CI workspace is a Staging one and reads qli and qli-staging, matching what the staged archive actually offers.
Closes: #93