Skip to content

v0.0.17

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Oct 01:43
v0.0.17
This tag was signed with the committer’s verified signature.
ayagmar Abdeslam Yassine Agmar
SSH Key Fingerprint: 8jYZ/oL1VWYmHpSUKk+sOgX9gTPRXK9vKxz/Ht6hzs8
Verified
Learn about vigilant mode.
77b7903
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

runnerd 0.0.17

What changed

  • Auto sizing moves cpus on each job's average CPU, not on its CPU peaks (#122, ADR 0068). Parallel builds spike to any cap, so the old rule only ever raised cpus; on one host it took a JVM profile from 16 to 31 CPUs in a day while its jobs averaged 7.5. A raise now needs a job averaging 70% of its cap, and a profile far under its cap steps down by max_step a day. A raise the slice or the CPU budget cannot hold is not written, and every client says why.
  • A job cancelled before any runner took it reads cancelled in queue instead of elsewhere, with no start or run time (#121, ADR 0069).
  • The JIT config is no longer in any process's arguments (#121). It reached run.sh and the listener as --jitconfig, readable by every host user through ps; it is now passed in an environment variable the runner removes before starting a job.
  • Reseeds are safe to interrupt and keep deletions (#119, #120, ADRs 0066 and 0067). A reseed that did not finish starts the profile over from the image, and image files a job deleted stay hidden after a reseed.

Upgrading

The job history stays at version 13. Install 0.0.17 with install.sh --version v0.0.17, move each profile's image to its -0.0.17 tag and restart runnerd. Going back to an older image afterwards needs the profile's snapshot and slot volumes removed. Details: Upgrading.

Download runnerd 0.0.17

File Platform Checksum
runnerd-aarch64-unknown-linux-musl.tar.xz ARM64 MUSL Linux checksum
runnerd-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo ayagmar/runnerd

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo ayagmar/runnerd

runnerd-cli 0.0.17

Download runnerd-cli 0.0.17

File Platform Checksum
runnerd-cli-aarch64-unknown-linux-musl.tar.xz ARM64 MUSL Linux checksum
runnerd-cli-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo ayagmar/runnerd

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo ayagmar/runnerd
Assets 14
Loading