You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Hydra cluster with many build slaves that each have interesting "features" (hardware.) I would like to be able to interactively run tests on these machines, in addition to the Hydra tests.
For example I would like to be able to run nix-build on my laptop and have it execute the test on one of the build slaves that can satisfy the required features. Ideally an interactive test would be time limited (e.g. timeout 60 nix-build ...) and would preempt any automatic build from Hydra (but in such a way that it will be automatically retried later.) The idea is that most of the time machines will be running automatically scheduled tests but occasionally this will be interrupted for an interactive test.
How realistic is this dream? :-)
The text was updated successfully, but these errors were encountered:
By "interactively" I suppose that I mean "synchronously and with low latency."
So I would write nix-build-on-hydra foo.nix to submit a job for Hydra to run now and the command would wait while it builds and then finally import the results into my local nix store.
This differs from normal distributed nix via the build hook because Hydra is the one keeping track of what build slaves exist, what are their supported features, how they should prioritize work, etc. also in that the derivations will be built completely with only the final result being imported into my local store.
I have a Hydra cluster with many build slaves that each have interesting "features" (hardware.) I would like to be able to interactively run tests on these machines, in addition to the Hydra tests.
For example I would like to be able to run
nix-build
on my laptop and have it execute the test on one of the build slaves that can satisfy the required features. Ideally an interactive test would be time limited (e.g.timeout 60 nix-build ...
) and would preempt any automatic build from Hydra (but in such a way that it will be automatically retried later.) The idea is that most of the time machines will be running automatically scheduled tests but occasionally this will be interrupted for an interactive test.How realistic is this dream? :-)
The text was updated successfully, but these errors were encountered: