hydra: Evaluate jobsets in Rust - #1940
Open
Ericson2314 wants to merge 2 commits into
Open
Ericson2314 wants to merge 2 commits into
Ericson2314 wants to merge 2 commits into
Conversation
Ericson2314
force-pushed
the
more-rust-eval
branch
from
September 26, 2026 16:37
8cfb4f4 to
59175d6
Compare
…rocess Two parts of `hydra-eval-jobset` become programs of their own, which it now runs: - `hydra-fetch-input` fetches inputs of plugin-provided types, one request at a time over JSON on standard streams, with one worker for the whole run. - `hydra-prepare-declarative-jobset` fetches a declarative project's specification and applies it, either creating the jobsets it names or reconfiguring `.jobsets`. These are the two parts that must stay Perl: input plugins are written in Perl, and the declarative helpers are shared with `hydra-notify`'s `DeclarativeJobsets` plugin. Moving them out first means replacing the rest of `hydra-eval-jobset` doesn't also have to move them. Behaviour is unchanged, and `hydra-eval-jobset` no longer loads plugins itself.
What remained of `hydra-eval-jobset` is now Rust, in `hydra-evaluator`, which runs `hydra-fetch-input` and `hydra-prepare-declarative-jobset` for the parts that must stay Perl. The Rust is meant to behave the same as the Perl did. Comments mark the places where matching it took extra work. There are two intended changes: - `hydra-evaluator <project> <jobset>` evaluates a single jobset, and exits non-zero if the evaluation fails. - `sysbuild` inputs work now. The Perl called a result set that doesn't exist, so they always failed. The evaluator's settings move from `hydra.conf` to `/etc/hydra/evaluator.toml`, and Hydra warns about any left behind. Assisted-by: Claude Code (Opus 5.5)
Ericson2314
force-pushed
the
more-rust-eval
branch
from
September 26, 2026 18:11
59175d6 to
55489ef
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Most of what
hydra-eval-jobsetdid doesn't need Perl. Fetching inputs does, because input plugins are written in Perl. Declarative projects need it too: their specification is fetched through a plugin, then applied by Perl helpers thathydra-notify'sDeclarativeJobsetsplugin also uses. Those two jobs become small scripts that the evaluator runs,hydra-fetch-inputandhydra-prepare-declarative-jobset. Everything else is now Rust, inhydra-evaluator.The Rust is meant to behave the same as the Perl did. Comments mark the places where matching it took extra work.
There are two intended changes:
hydra-evaluator <project> <jobset>evaluates a single jobset, and exits non-zero if the evaluation fails.sysbuildinputs work now. The Perl called a result set that doesn't exist, so they always failed.The evaluator's settings move from
hydra.confto/etc/hydra/evaluator.toml, and Hydra warns about any left behind.Assisted-by: Claude Code (Opus 5.5)