ci: support CI on wrynose#37
Open
Ricardo Salveti (ricardosalveti) wants to merge 5 commits into
Open
Conversation
Ricardo Salveti (ricardosalveti)
requested a review
from Nicolas Dechesne (ndechesne)
as a code owner
|
This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time. |
|
This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time. |
|
Is this one still relevant? |
Collaborator
Author
Yup, was waiting to clear out the CI first (which is done now), will work on this one again. |
Update the meta-qcom repo pin in the kas fragments to track the wrynose LTS branch. All other upstream layer branches (openembedded-core, bitbake, meta-openembedded, etc.) and the base.lock.yml pins are inherited from meta-qcom's own ci fragments through the kas includes, so no other change is needed on this side. Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
For push and pull_request events, GitHub runs the workflow file from the pushed branch (push) or the PR's base branch (pull_request). The wrynose copies of these workflows therefore only ever evaluate for wrynose, so listing main in their branch filters is unreachable dead config. Point the push, pr, qcom-preflight-checks, and markdownlint branch filters at wrynose only. The main branch carries its own copies listing only main. Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
GitHub Actions only runs schedule-triggered workflows from the repository's default branch (main), so this copy never executes from wrynose. Main already carries the copy that actually runs; keeping an inert duplicate here only creates drift and confusion. Remove it so wrynose carries only the workflows that run from it. Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
Document the wrynose LTS branch in the Branches section: it tracks the Yocto Project 6.0 LTS release and is used by Qualcomm Linux 2.x. Update the layer dependencies to point at the wrynose branches of openembedded-core and meta-qcom, matching what the CI builds against. The "Build on push" and "Nightly Build" badges defaulted to the repository default branch (main). On the wrynose branch they should reflect wrynose CI status instead, so add branch=wrynose to the shields.io image URLs and query=branch:wrynose to the workflow links. Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
wrynose is the LTS Stable branch, where backporting from main is the default contribution path, mirroring the workflow established in meta-qcom. Add BACKPORTING.md as the source of truth for the backport workflow: the git cherry-pick -x path from main, the exception for wrynose-only changes, the CI-equivalent checks to run before opening a PR, and the [Backport wrynose] commit message conventions. Adapt AGENTS.md with the LTS callout and rework the contribution section to point at BACKPORTING.md, adapt the docs/contributing.md introduction and upstream target branch accordingly, and reference the backport workflow from the README Contributing section. Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
Ricardo Salveti (ricardosalveti)
force-pushed
the
wrynose-ci
branch
from
1b24086 to
ddbe8bb
Compare
Ricardo Salveti (ricardosalveti)
requested review from
Koen Kooi (koenkooi),
Dmitry Baryshkov (lumag) and
Jose Quaresma (quaresmajose)
Dmitry Baryshkov (lumag)
approved these changes
Jul 9, 2026
Jose Quaresma (quaresmajose)
approved these changes
Jul 9, 2026
Contributor
|
Nicolas Dechesne (@ndechesne) , could you please take a look? |
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
4 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.
Current CI settings are specific to main, separate workflows so they can be branch based and add support for specific wrynose-based workflows.