Packaged Kernel CI: Current Status and Next Steps
This session will present what is the current status of the packaged kernel CI, presenting how it's currently producing the packaged kernel trees and packages, and discuss what might still be missing for a full CI.
https:/
Suggestion for Topics:
* Enabling Cross packages
* Pushing cross-generated packages to LAVA
* Only generate deb packages from known-to-be-working trees
Blueprint information
- Status:
- Not started
- Approver:
- Ricardo Salveti
- Priority:
- Undefined
- Drafter:
- John Rigby
- Direction:
- Needs approval
- Assignee:
- John Rigby
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Notes from the session:
Packaged Kernel CI: Next Steps
Current issues:
Changelog: Improve it in a way we can point first the most important part for both the users and the LTs
Meta Packages: Should also be generated automatically as well with the kernel CI, and published to the Kernel PPA as well
Shared:
* Created by the common linux-linaro jenkins build, ABI is moved automatically
* Problem when validating the trees, as one can easily block the others
* Stop generating shared and keep producing both headers and tools by each flavor
Next Steps:
* Split it into 2 jobs: 1 - cross build and validation, 2 - push the src packages to launchpad
* Cross build
- Just need to enable it
* LAVA validation before publishing the src package to Launchpad
- What kind of test cases:
* Boot
* LTP?
* Enablement? Wifi, BT and such
- Only the boot test case should block the package promotion
