Skip to content
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

Add branch ci/* or kernelci from https://github.com/compudj/linux-dev #2698

Open
kienanstewart opened this issue Oct 4, 2024 · 1 comment · May be fixed by kernelci/kernelci-pipeline#905
Assignees

Comments

@kienanstewart
Copy link

Please provide the information described below in order to add a new branch to
kernelci.org:

  • Which Git branch do you want to add?

⇨ Git repo URL: https://github.com/compudj/linux-dev

⇨ Git branch name: pattern ci/*, or if that's not possible: kernelci

  • How much build coverage do you need for your branch?
  1. Build only the main defconfig for each architecture to save a lot of build
    power, get the fastest results and highest boots/builds ratio. This is what do
    with some maintainer branches such as linusw' GPIO branch.

⇨ Build coverage choice: 3 (defconfig for each arch)

  • How often do you expect this branch to be updated?

⇨ Estimated frequency: A few times each week

  • Who should the email reports be sent to?

⇨ Recipients: [email protected]

@nuclearcat nuclearcat self-assigned this Oct 23, 2024
nuclearcat added a commit to nuclearcat/kernelci-pipeline that referenced this issue Nov 22, 2024
As requested in kernelci/kernelci-core#2698
Adding tree https://github.com/compudj/linux-dev, with branch kernelci,
as wildcards is not supported yet.

Signed-off-by: Denys Fedoryshchenko <[email protected]>
@nuclearcat
Copy link
Member

Hello, during staging verification our tools reported that kernelci branch doesn't exist.

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 a pull request may close this issue.

2 participants