ci: publish production kernel debs as rolling GitHub release#320
Open
anodos325 wants to merge 1 commit into
Open
ci: publish production kernel debs as rolling GitHub release#320anodos325 wants to merge 1 commit into
anodos325 wants to merge 1 commit into
Conversation
On push to truenas/linux-6.18 or stable/26, republish the production debs as assets of a per-train rolling prerelease (master-nightly, 26-nightly) with SHA256SUMS and a manifest.json naming the kernel release and files. Unlike Actions artifacts, release assets never expire and are downloadable anonymously at stable URLs, so downstream builds can consume the latest kernel without credentials. Tags follow the TrueNAS train rather than the kernel series so that consumer download URLs survive a kernel-series rebase of master; a branch-to-train case mapping fails the job on any unmapped branch. Align the production build with truenas_build (conf/build.manifest): set EXTRAVERSION/PYTHON via the environment, replace distclean with rm -rf .config.old, use plain make defconfig, add zstd. Force the production build on publishing-branch pushes so a skip-duplicate result cannot leave the publish job without artifacts. The publish job refuses to run if the branch tip has moved on, and a concurrency group serializes back-to-back merges. Package names carry no kernel version, so the release string is read from the vmlinuz path inside the image deb.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On push to truenas/linux-6.18 or stable/26, republish the production debs as assets of a per-train rolling prerelease (master-nightly, 26-nightly) with SHA256SUMS and a manifest.json naming the kernel release and files. Unlike Actions artifacts, release assets never expire and are downloadable anonymously at stable URLs, so downstream builds can consume the latest kernel without credentials.
Tags follow the TrueNAS train rather than the kernel series so that consumer download URLs survive a kernel-series rebase of master; a branch-to-train case mapping fails the job on any unmapped branch.
Align the production build with truenas_build (conf/build.manifest): set EXTRAVERSION/PYTHON via the environment, replace distclean with rm -rf .config.old, use plain make defconfig, add zstd.
Force the production build on publishing-branch pushes so a skip-duplicate result cannot leave the publish job without artifacts. The publish job refuses to run if the branch tip has moved on, and a concurrency group serializes back-to-back merges.
Package names carry no kernel version, so the release string is read from the vmlinuz path inside the image deb.