Repository navigation
ci: publish executable hashes and refresh the eBPF allowlist on release - #585
Conversation
The allowlist is built from the published hashes, so new releases are allowed without updating the macro runner agent. Refs COD-3826
Merging this PR will not alter performance
|
|
Publish the SHA-256 of every released executable as a release asset, then ask app.codspeed.io to rebuild its eBPF allowlist.
CodSpeed only lets approved executables load eBPF on its runners. Until now that list was pinned by hand, so every memtrack release needed a manual approval step. With the digests published on the release, the allowlist is derived from them and a new release is approved as soon as the workflow runs.
Each asset is named
<executable>-<target>.sha256.sumand holds onesha256sumline (<hex> *<executable>), hashed from the binary inside its release archive. The memtrack releases frommemtrack-v1.4.0tomemtrack-v1.6.1were backfilled with the same files.Needs the
EBPF_ALLOWLIST_REVALIDATE_TOKENrepository secret before the next release.Refs COD-3826