| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Now that we're requiring CI to verify all changes (yay) it's not
actually possible to push and submit in one go - this repurposes the
rubberstamp command to push and self-+2, which is still useful for
self-owned things like system config etc.
Change-Id: Ie064adb6b7b0c1fd6bffdf4583a201ea02d4f8ac
Reviewed-on: https://cl.tvl.fyi/c/depot/+/939
Tested-by: BuildkiteCI
Reviewed-by: tazjin <mail@tazj.in>
|
|
Don't want this getting GCed in between execution, so remove
--no-out-link from the nix-build invocation.
Change-Id: Ib786d46f84938f45f51823781eecb88338120526
Reviewed-on: https://cl.tvl.fyi/c/depot/+/943
Reviewed-by: glittershark <grfn@gws.fyi>
|
|
Change-Id: Id1107c13f10726ecb8a14c14e6532c17f0b5c54a
Reviewed-on: https://cl.tvl.fyi/c/depot/+/942
Reviewed-by: glittershark <grfn@gws.fyi>
|
|
Change-Id: I658ca00a9e5cdf69e884edb872816c192f794683
Reviewed-on: https://cl.tvl.fyi/c/depot/+/941
Reviewed-by: glittershark <grfn@gws.fyi>
|
|
This adds a first crack at one idea for a generic, non-user-specific
rebuild-system script to ops.nixos.rebuild-system. The idea here is that
we enumerate all the nixos systems stored in the monorepo (similarly to
what we do for ci-builds right now) then search through them by hostname
to find the one matching the hostname of the current system, which is an
attempt at a more generic version of tazjin's rebuilder script which
does the same thing but with an explicit case block.
As a caveat, it feels like there's a slight possibility that this way of
finding systems is going to get slow to evaluate - on my system it feels
fine but if it grows out of hand it's probably feasible to just bake
this into the built script as a dynamically generated case statement.
Change-Id: I2e4c5401913b6f4d936ab48ba2f95f96e0e78eb4
Reviewed-on: https://cl.tvl.fyi/c/depot/+/894
Tested-by: BuildkiteCI
Reviewed-by: lukegb <lukegb@tvl.fyi>
|
