Skip to content

Add qcom-next tree to run CI/CD on the next branch #1256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 17, 2025

Conversation

quic-ylal
Copy link
Contributor

Integrates the qcom-next tree to enable CI/CD workflows on the 'next' branch to
ensures validation of changes and improves stability across development iterations.

@nuclearcat
Copy link
Member

According to kci config forecast following builds will be done:

  Number of builds: 13
  Builds:
    - kbuild-clang-17-arm
    - kbuild-gcc-12-arm
    - kbuild-gcc-12-arm-build-only
    - kbuild-gcc-12-arm64
    - kbuild-gcc-12-arm64-kselftest-16k_pages
    - kbuild-gcc-12-arm64-build-only
    - kbuild-gcc-12-arm64-chromebook-kcidebug
    - kbuild-gcc-12-arm64-kselftest
    - kbuild-gcc-12-arm64-mainline-big_endian
    - kunit-x86_64
    - kbuild-gcc-12-arm64-chromebook
    - kbuild-gcc-12-arm64-chromeos-mediatek
    - kbuild-gcc-12-arm64-chromeos-qualcomm

Staging pass config checks, validator ok, so merging PR.

@nuclearcat nuclearcat added this pull request to the merge queue Jul 17, 2025
Merged via the queue into kernelci:main with commit b5fad38 Jul 17, 2025
4 checks passed
@@ -116,6 +116,9 @@ trees:
qcom:
url: "https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git"

qcom-next:
Copy link
Contributor

Choose a reason for hiding this comment

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

It would be great if you can limit it to run only on qcom devices in KernelCI

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.

3 participants