Repository navigation
Closed
Description
Summary
CI rebuilds FSDK's kernel (components/linux.bst) from source on every run: 62–93 min of a ~110 min build step, about 85–90% of the build job. On main its cache key doesn't change between runs (main runs 36640985380 and 36651111965 both built kernel key 641192ff), but CI only pulls from caches, so every run starts cold.
Pushing a safe subset of our artifacts to cache.projectbluefin.io from main should bring main's build step from ~108 min down to roughly 12–18 min. PR builds get the same benefit later, once they use a fixed dev module key (separate decision; the lab's bluefin-server-build-pipeline already does this).
What we need from a cache / org admin
- Upload credential for
projectbluefin/server. This uses the same mTLS scheme dakota uses (vars.CASD_CLIENT_CERT+secrets.CASD_CLIENT_KEY, uploading tohttps://cache.projectbluefin.io:11002). Ideally a server-specific client cert, so it can be revoked on its own. Please add it to this repo'sbst-cacheenvironment (already created; deployments restricted tomain):- environment variable
CASD_CLIENT_CERT(PEM client certificate) - environment secret
CASD_CLIENT_KEY(PEM client key)
- environment variable
- Capacity sign-off. We'd upload the kernel plus roughly 15 FSDK/bootstrap elements that FSDK's cache doesn't hold (go, binutils-stage1, elfutils, lvm2-base, …) and our own key-free elements (ignition, openzfs, k0s/kubeadm binaries, …). Most of these only change when FSDK is bumped or a pin moves. Measured sizes will be posted in the implementing PR.
- Confirm that artifacts uploaded on
:11002are served from:11001.:11001is the read-only endpoint already inproject.conf, so PR builds and local builds would pull them with no config change.
Safety design (implemented in the follow-up PR)
- Upload only from pushes to
main. Thebuildjob uses thebst-cacheenvironment only forpushevents onrefs/heads/main. The environment's deployment rule allows onlymain(enforced by GitHub), so a PR that edits the workflow still can't get the credential. Fork PRs never see secrets at all. - Nothing key-derived is uploaded. The upload step runs after the build, with an explicit allow-list: the full graph minus
bluefin-server/keys/boot-keys.bst, anything that usesfiles/boot-keys, and everything that depends on those (build or runtime). A unit test enforces this. The upload config is never active duringbst build; otherwise BuildStream would upload every artifact it builds, including the keys. - Missing credentials mean no upload. Until the environment has both values, the step logs that it is skipping and the build behaves exactly as it does today.
- Reproducibility is unaffected.
reproducibility.ymlalready rebuilds the final artifacts with--ignore-project-artifact-remotes.
Prior art
- dakota:
.github/actions/generate-bst-ci-config/action.yml(config generation, mTLS, upload flag),.github/workflows/build.yml(how the secrets are passed and gated). - lab:
argo/workflow-templates/bluefin-server-build-pipeline.yaml, which builds this repo with a fixed dev key "so a stable dev key keeps the kernel … in the BuildBarn CAS".
Metadata
Metadata
Assignees
Labels
No labels
Activity
kylerankin commentedon Sep 30, 2026
The shippable follow-up is ready: PR #302 (non-draft, base
main).It implements the safety design from the issue:
.github/scripts/bst-push-elements.py— explicit key-free allow-list, fails closed if any element is key-derived (boot-key element,files/boot-keys, or a transitive build/run dependency of either)..github/workflows/build.yml, gated to pushes onrefs/heads/mainbehind thebst-cacheenvironment; clean skip with no behavior change when credentials are absent.tests/unit/test_bst_push_allowlist.pyenforces the invariant on the real graph (207 passing).The three admin asks are left for you: create/point the
bst-cacheenvironment at a revocable server-specific client cert, capacity sign-off, and confirm:11001vs:11002.— hive: backend=pi model=lemonade/Ornith-1.5-35B-A3B-GGUF-Q6_K
🐝 Hive Agent:
contributor| SHA:4892da5Danathar commentedon Sep 30, 2026
Heads-up: there are two open PRs for this issue, and neither links to the other.
bst show --deps allin.github/scripts/cache-push-allowlist.pyand pushes from thebuildjob. Its CI ran green at8956ec3..github/scripts/bst-push-elements.py) and a separate main-onlyartifact-pushjob. It's waiting on two human decisions: the job layout, and whether publishing the BuildStream cache as an Actions artifact is acceptable.Both are now conflicting with
main. Choosing one approach before either gets rebased would save a round of work.dtg01100 commentedon Oct 2, 2026
smoke test
🐝 Hive Agent:
contributor| SHA:9994af8fix(ci): make bst-cache environment valid; fix probe parsing
jeefy commentedon Oct 3, 2026
Status: #365 (ahmedadan) now seeds the kernel and Go into
cache.projectbluefin.io:11002over mTLS from thekernel-cachejob, and builds pull them throughproject.conf's remotes. That's the main win this issue was after, so #301 (closed) is no longer needed. Open follow-up from #355: moveCASD_CLIENT_KEYinto a GitHub Environment that onlymaincan deploy to (this repo already hasbst-cache, restricted tomain), attach that environment to thekernel-cachejob, and delete the repository-level secret. That needs the key's value, so an admin has to do it. Then this can close.jeefy commentedon Oct 6, 2026
Done. #365 seeds the kernel and Go into the project cache from
main. #404 also seeds the dev-key kernel, so PR and nightly builds can reuse it. The remaining step, moving theCASD_CLIENT_KEYvalue into thebst-cacheenvironment, is documented indocs/skills/ci-tooling.md.