Repository navigation
Conversation
|
Label |
0406970 to
b703ae1
Compare
|
🌿 Preview your docs: https://nvidia-preview-pr-4603.docs.buildwithfern.com/openshell |
|
/ok to test b703ae1 |
|
Label |
PR Review StatusThe initial independent code review found no blocking defects in the Cachix credential isolation changes. Required CI is now running on the current-head mirror after @SDAChess, I checked your questions about the regression test and the length of the CI documentation. The test guards credential placement and step ordering; the documentation explains the external environment restrictions that YAML cannot enforce. Those comments remain open for discussion with the author; Gator has not resolved your threads. Blocking findings: None. Carried findings: None. Gator metadata
|
|
/ok to test 5939f69 |
PR Review StatusThe independent follow-up review found no blocking issues in the documentation-only changes since the previous review. @alangou, I checked your update about shortening the CI guidance: it retains the credential migration, protected environment, and read-only cache requirements; the regression test remains in place as you described. I refreshed the test mirror for the latest head. Branch Checks and Helm Lint are queued, and the current-head E2E run is pending; required checks must finish before the maintainer handoff. Blocking findings: None. Carried findings: None. Gator metadata
|
|
/ok to test 910a024 |
|
Label |
PR Review StatusThe independent follow-up review found no blocking issues in the removal of the Cachix isolation checker and its CI, task, and documentation references. @alangou, I checked your latest test-removal commit: it leaves the credential isolation workflow unchanged and removes the associated task references consistently. The test mirror now matches the latest head, and I re-applied Action required: A maintainer must re-run failed jobs in PR Issue Acceptance. Workflow reruns have not been explicitly authorized for this watcher. Blocking findings: None. Carried findings: None. Gator metadata
|
Make shared Nix setup read-only and populate the cache from main in a dedicated environment. Remove write-token forwarding from reusable workflows and cover the boundary with regression tests. Requires revoking the legacy token and provisioning cachix-write as documented in CI.md. Signed-off-by: Adrien Langou <alangou@nvidia.com>
Preserve action order and multiplicity when checking the credential-bearing cache writer. Require immutable action revisions and cover candidate checkout/restore and reordered-step regressions. Signed-off-by: Adrien Langou <alangou@nvidia.com>
Signed-off-by: Adrien Langou <alangou@nvidia.com>
Signed-off-by: Adrien Langou <alangou@nvidia.com>
910a024 to
42df333
Compare
|
/ok to test 42df333 |
PR Review StatusThe independent critical-only follow-up found no new Critical defects in the author-only delta after the rebase. The release workflow changes consistently remove cache write-token forwarding; no prior Gator findings remain open. @alangou, I checked your latest mirror refresh: it matches this head, PR Issue Acceptance now passes, and Branch Checks and the required E2E suite are running. The earlier CI infrastructure blocker has cleared. Maintainer approval remains outstanding after the required checks finish. Blocking findings: None. Carried findings: None. Gator metadata
|
Summary
Make shared Nix setup read-only and move Cachix population into a dedicated workflow that runs from
main. Branch, release, and scan jobs continue to use the cache without receiving its write credential.Related Issue
Internal tracking: 041 (private review).
Changes
main-only cache population workflow using the protectedcachix-writeenvironmentCI.mdBefore enabling cache writes, complete the
cachix-writeenvironment setup and remove the legacy repository credential as documented inCI.md.Testing
mise run --skip-tools test:cachix-isolation(8 passed)ty check tasks/scripts/check_cachix_isolation_test.pyChecklist
CI.md)