Skip to content

ci/world: add qcom-distro - #2199

Closed
Jose Quaresma (quaresmajose) wants to merge 1 commit into
qualcomm-linux:masterfrom
quaresmajose:world
Closed

Jose Quaresma (quaresmajose) wants to merge 1 commit into
qualcomm-linux:masterfrom
quaresmajose:world

Conversation

@quaresmajose

@quaresmajose Jose Quaresma (quaresmajose) commented May 14, 2026

Copy link
Copy Markdown
Contributor

We also need to validate that everything in qcom-distro continues to
function whenever changes are submitted.

@github-actions

Copy link
Copy Markdown

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.

@lumag Dmitry Baryshkov (lumag) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't build:

ERROR: Nothing PROVIDES 'Qualcomm-XFCE-demo-image'
ERROR: Required build target 'qcom-xfce-demo-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['qcom-xfce-demo-image', 'Qualcomm-XFCE-demo-image']

But, frankly speaking, I think this belongs only to meta-qcom-distro.

@quaresmajose

Copy link
Copy Markdown
Contributor Author

Yeah, fix proposed in qualcomm-linux/meta-qcom-distro#409

@lumag Dmitry Baryshkov (lumag) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a part of qcom-distro rather than meta-qcom.

@quaresmajose

Copy link
Copy Markdown
Contributor Author

This should be a part of qcom-distro rather than meta-qcom.

I disagree. Since the qcom-distro layer is also under our control and in our responsibility, we must prevent regressions originating from the BSP layer and also from all the other other layers which are controlled here by kas.

@lumag

Copy link
Copy Markdown
Contributor

Yes. However it should be done other way, like we discussed in Torino: moving integration CI to qcom-distro.

If we merge this, then merging anything in case of major breakage affecting several layers would become very troublesome.

@lumag

Copy link
Copy Markdown
Contributor

In my opinion, CI should exactly follow the layer dependencies. Meta-qcom depends only on OE-core, so it should also build and verify against OE-core only. The distro has multiple dependencies, binding then together. Then the distro should build and test the integration.

@quaresmajose

Copy link
Copy Markdown
Contributor Author

I also agree with that, but currently there are already some discrepancies between the CIs, and the one from meta-com is the one in the best condition.

@quaresmajose

Copy link
Copy Markdown
Contributor Author

Yes. However it should be done other way, like we discussed in Torino: moving integration CI to qcom-distro.

We keep adding more things, but they still don't go in that direction, I should change my priorities for this, but new things keep popping up.

I'll put it in draft mode just for myself while I fix the pending build issues.

We also need to validate that everything in qcom-distro continues to
function whenever changes are submitted.

Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>
@quaresmajose

Copy link
Copy Markdown
Contributor Author

Proproposed in qcom-distro qualcomm-linux/meta-qcom-distro#469

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants