Make hydra fail early on unsupported platforms

I yesterday set up a personal hydra to play around with it on my laptop, hoping to be able to set one up later on a beefier machine.

While doing this, I did some small fails in describing the job and accidentally provided buildjobs for aarch64-linux and x86_64-darwin which both started with doing about a thousand build inputs each before they eventually failed with “unsupported platform”.

Is there a way to make hydra fail much earlier? Before it starts wasting time and bandwidth downloading gigabytes of stuff, when no compatible build host is available?

1 Like