vpn-mx: put the ymrtech build gate's ruby toolchain in the system profile (ymrtech#948) #1977
No reviewers
Labels
No labels
backlog
bug
enhancement
in-progress
review
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ymrtech/nix-config!1977
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kb/YMRT-948-icon-coverage-ruby"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Card ymrtech#948, second half of the same fix as #1976 (already merged).
A
[ci]job's PATH is its runner DAEMON's env, frozen at daemon start and never refreshed by a switch (stopIfChanged/restartIfChanged = falseon the runner units). MEASURED with a throwaway probe workflow on branchprobe/YMRT-948-ci-ruby-env(run 14962, three[ci]jobs):command -v rubyand the PATH probe b saw was the hostPackages list from BEFORE even attic-client was added — no ruby, and no
/run/current-system/sw/bin. So #1976's hostPackages entry is correct but inert until that daemon restarts, which the fleet's runner units deliberately never do.Same shape as the jq/attic-client entries already in this file: the tool goes in the SYSTEM PROFILE (which every switch DOES refresh) and the job prepends it — the fleet idiom (
export PATH="/run/wrappers/bin:/run/current-system/sw/bin:$PATH", used in ten workflow steps today).The matching ymrtech-side change (a guarded prepend step in the four jobs, active only where
rubyis not already on PATH) follows as a separate PR in the ymrtech repo.