!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

393 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.120 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
26 Dec 2025
@hexa:lossy.networkhexaA propos ofborg15:47:55
@hexa:lossy.networkhexa @janne:hess.ooo we have to m1 minis in transit that we could allocate to ofborg 15:48:14
@gabyx:matrix.orggabyx

IMO: Also to consider is the following when switching to a new CI:

  • You actually would like to drive the whole Pipeline by code (ideally typed) not YAML.
    Several methods to achieve that, certain providers are able to do dynamic pipelines (which might take slight overhead, dep. on how fast the jobs are and the pipeline generation).
    This gives some much better observability/maintainability in the long term etc. (In our projects we only do that, with Gitlab and only Nix, and with Go)
    Maybe even simplesr for nixpkgs, a tool which just generates a bunch of derivations to build which are the CI jobs, (could be anything, linting, testing, formatting etc... )?
15:48:50
@hexa:lossy.networkhexamaybe we could also kill x86_64-darwin early and prioritize aarch64-darwin15:49:13

Show newer messages


Back to Room ListRoom Version: 6