Skip to content

Conversation

sampra2025
Copy link

This setup will help to validate the meta-qcom GH workflows, end to end on AWS Stage environment.

* Created a fork of meta-qcom as "aws-meta-qcom" under qualcomm-linux-stg organization.
* Created a new branch as "qli-validation" to update the workflow settings
* modified build-yocto.yml to use "aws-meta-qcom" repo
* Remove nightly build schedule and updated with on demand build

Copy link

@upstream-ci upstream-ci left a comment

Choose a reason for hiding this comment

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

Looks good

@sampra2025 sampra2025 force-pushed the qli-validation branch 3 times, most recently from f8b0fc4 to 4d1ed79 Compare September 11, 2025 16:15
@sampra2025 sampra2025 force-pushed the qli-validation branch 2 times, most recently from 6354fec to 09dd21a Compare September 25, 2025 19:21
@sampra2025 sampra2025 force-pushed the qli-validation branch 2 times, most recently from f8aa3f6 to 596d77a Compare October 8, 2025 23:42
This setup will help to validate the meta-qcom GH workflows, end to end
on AWS Stage environment.

    * Created a fork of meta-qcom as "aws-meta-qcom" under qualcomm-linux-stg
    organization.
    * Created a new branch as "qli-validation" to update the workflow settings
    * modified build-yocto.yml to use "aws-meta-qcom" repo
    * Remove nightly build schedule and updated with on demand build
    * Commented out the upload artifact step from action.yml
    * changed runner label to use non SSD instance

Signed-off-by: Satish Mhaske <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants