search

NixOS / hydra

Hydra, the Nix-based continuous build system
http://nixos.org/hydra
GNU General Public License v3.0
1.1k stars 291 forks source link

Hydra dual writes to >= 2 locations #1367

Open RaitoBezarius opened 4 months ago

RaitoBezarius commented 4 months ago

Is your feature request related to a problem? Please describe.

The write path counterpart of NixOS/infra#394.

In preparations for experimenting on alternative store backends, it is necessary to enable Hydra to write the same produced contents to multiple store targets, e.g. the primary S3 backend and another S3 in another place.

Describe the solution you'd like

(1) Hydra gets supported to copy the outputs to multiple locations, ideally in "parallel" (2) Direct access to the secondary (and more) location provides the expected files on a local deployment (NixOS test?) (3) Suggest a change to NixOS configuration of Hydra in this repo

Describe alternatives you've considered

Additional context

Garbage collection policies on targets are yet to be determined, if there's a background process GCing the alternative stores, the situation where Hydra tries to insert too many things can happen before GC is not aggressive enough, conversely, if Hydra is responsible to GC when it cannot push into, we are mixing GC policies inside the CI software...

delroth commented 4 months ago

(1) Hydra gets supported to copy the outputs to multiple locations, ideally in "parallel"

IMO we could get away with it not being done in parallel (Hydra has far more than enough parallelism as it is to keep itself busy), what is non-negotiable is that it needs to be compressing only once, and I think this might require some fairly deep changes to Nix itself since Hydra mostly leaves Nix in charge of doing the store writes. Hopefully not...

zimbatm commented 4 months ago

It's probably easier to have one box receive and multiplex the uploads

ajs124 commented 4 months ago

If you want hydra itself to do this, one relatively easy way to configure this could be with a RunCommand. They run as part of hydra-notify. Some documentation for them is here. Having long running ones shouldn't be an issue in my experience, but I don't know enough about how the plugin architecture works, to say for sure if this would be a good idea.