]> git.ipfire.org Git - thirdparty/ipxe.git/commit
[ci] Publish rolling release build artifacts with stable URLs coverity_scan master rolling/bin rolling/bin-arm32-efi rolling/bin-arm64-efi rolling/bin-combi rolling/bin-i386-efi rolling/bin-loong64-efi rolling/bin-riscv32 rolling/bin-riscv32-efi rolling/bin-riscv64 rolling/bin-riscv64-efi rolling/bin-x86_64-efi rolling/bin-x86_64-pcbios
authorMichael Brown <mcb30@ipxe.org>
Thu, 29 Jan 2026 14:50:32 +0000 (14:50 +0000)
committerMichael Brown <mcb30@ipxe.org>
Fri, 30 Jan 2026 00:03:35 +0000 (00:03 +0000)
commit74e0551ac2f66760430e69407a4f7ed0dfe9feab
treececcc76fbf583e892351aa86295069cfcfa0654d
parente855c4c64237619a43c2850bd20c81e4796850f8
[ci] Publish rolling release build artifacts with stable URLs

Publish the binaries built from commits on the master branch under
stable URLs such as:

  https://github.com/ipxe/ipxe/releases/download/rolling/bin/undionly.kpxe

Since filenames such as "ipxe.iso" may exist in each of several build
directories, we implement this as one release tag per build directory.
The GitHub Actions workflow automatically moves the tag to the most
recent commit and overwrites the existing release assets.

One downside of this is that running a local "git log" or similar may
show a large number of uninformative tags of the form "rolling/bin",
"rolling/bin-x86_64-efi", "rolling-arm64-efi", etc, all pointing at
the most recent commit.  This clutter may be hidden using:

  git config --local log.excludeDecoration refs/tags/rolling/*

To avoid the unintentional creation of rolling release tags on forks,
we skip the whole publication job unless the environment variable
ROLLING_PREFIX is defined.

Signed-off-by: Michael Brown <mcb30@ipxe.org>
.github/workflows/build.yml