superconfig/.github/workflows/ at 1a69285cd52a22180a9f8dfaf9130e18e654e658 · lass.pds.lassul.us/superconfig · Tangled

lass.pds.lassul.us / superconfig

0

This repository has no description

0

superconfig / .github / workflows

5 files

at 1a69285cd52a22180a9f8dfaf9130e18e654e658

Hermes tools.hermes-voice: build, sign and publish the Android APK in CI 1d ago

assist-android.yml

tools.hermes-voice: build, sign and publish the Android APK in CI .github/workflows/assist-android.yml builds packages.hermes-voice-android on master pushes that touch it (and on demand) with the run number as versionCode and the short commit as versionName, signs it with hermes-voice-android-sign from the ANDROID_KEYSTORE_B64 and ANDROID_KEYSTORE_PASSWORD secrets (the clan var hermes-voice-android-signing of coaxmetal) and uploads it as assist.apk of the rolling release assist-android. The package takes versionCode and versionName (default 1), so `nix build .#hermes-voice-android` stays pure; CI overrides them through --impure --expr. The unsigned APK is also a check, so PR CI builds it.

1 day ago

.github.ci: evaluate the machines with iets eval-jobs iets (numtide/iets, a Nix evaluator in Rust) gives the same drvPath, isCached and cacheStatus for every machine as nix-eval-jobs 2.35.4, in 24-35s instead of 108-144s (4 workers, coaxmetal). It is a flake input so CI builds it once and pushes it to cache.lassul.us with niks3 and the lazy store.

2 days ago

.github.hestia-gc: init Daily garbage collection of the hestia cache on the default branch, after hestia's own gc.yml, so ci.yml's cache stays within the 10 GB GHA cache quota.

3 days ago

unmaintained-graph.yml

ci: publish unmaintained-graph to GitHub Pages

2 weeks ago

update-pkgs.yml

.github.ci: build the NixOS machines on plain runners with hestia Replaces the farm call. eval evaluates the new ciToplevels output once with hestia's matrix subaction (the same machines the farm built: all nixosConfigurations), shared builds the derivations needed by more than one uncached machine once and hands the hestia manifest version with their outputs to the machine jobs, one job per uncached machine builds its toplevel by drv path. The ci job stays the required check; shared and the machine jobs are skipped when nothing is uncached. Every job pushes the store paths it added, built or substituted from hestia, to niks3 with its GitHub OIDC token, as the farm did, so deploys find the toplevels in cache.lassul.us. The niks3 client is the new packages.niks3 output. Measured on the ci-hestia-shared experiment with a nixpkgs bump: 15 min (eval 3.3, shared 3.3, 1-4 per machine) instead of 49 with the farm. No more queueing of runs for the farm.

3 days ago