Open
Conversation
Contributor
|
note for my future self: riscv64-(33|34) are the fast ones, the others are slow. |
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
2 participants
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.
This PR adds support for tagging workers with arbitrary tags and filtering jobs that are dispatched to them. Each worker can have between 0 to N tags, and each tag can be associated with 0 to N tag rules.
A tag rule acts as a gatekeeper for rebuild jobs, preventing any jobs that do not match the name pattern and the optional version pattern from being picked up by the worker. In the proposed implementation, this means that a tagged worker will not pick up any untagged jobs.
Untagged workers exclusively pick up jobs that do not match any tag rules.
Tags and tag rules can be managed via the REST API or rebuildctl.