Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2673

The sccache client configuration is derived from the selected offer, local disk first

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
development-runtime
Milestone status
ACTIVE
Wave
2
Waiting on
I2670I2672
Holds back
I2676
Behind it in all
1
Evidence
0 of 2
In the waySubjectDetail
issueI2670I2670 is not DONE
issueI2672I2672 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2673

majordomus plan verify I2673

majordomus plan done I2673

What it is

Objective
Emit the sccache environment for the chosen offer through majordomus env, local as level one and the offer as level two, with no hand-set variable.
Why
The owner, 2026-10-13, with full clearance: set up MinIO, an sccache server and every mesh node, verified and validated. The cluster compiles the same Rust on every machine from a cold cache; two declared offload hosts were under their disk minimum that day. See ADR 0157.
Now
Measured on master b29cf4e487 on 2026-10-13: RUSTC_WRAPPER=sccache is set by the user's ~/.cargo/config.toml with no remote; environment/shell.rs exports nothing about it.
Wanted
majordomus env exports the derived configuration when sccache is present and an offer is selected, local-only otherwise, and a diagnostic when sccache is absent; the committed .envrc is unchanged; a user's cargo config is never edited.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • With an offer selected the exported variables name it and the local level and no secret is printed
  • With no offer the client is local-only
  • With the offer unhealthy at the moment the sccache server would start, the second level is left out and the compile succeeds: measured on 2026-10-13, a server started with a down store fails the compile (exit 2)
  • A store that stops while the server runs leaves the compile correct (measured: a miss, exit 0)
  • The installed sccache's multi-level support is read from the executable, not assumed
  • Cross-checkout path normalisation is investigated and the finding recorded
Validation
bin/majordomus plan validateMJ_TEST_JOBS=2 bash test/run.sh 3013_a_mesh_build_cache
Evidence required
client_derivation_casesccache_multilevel_measured
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/environment/docs/ENVIRONMENT.md
Not
Writing ~/.cargo/config.tomlDistributed compilation
Depends on
I2670I2672
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-13
Updated
2026-10-13
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.