Skip to content

Conversation

@tarkah
Copy link
Collaborator

@tarkah tarkah commented Dec 19, 2025

Most of this commit revolves around removing the
shared service::Config as each service should
have its own config so we can easily extend them
& not deal w/ unrepresentable states.

The rest revolves around being able to associate
a size to both builders & tasks (recipe names)
so that we can intelligently queue up builds on the correct sized builder.

SIGHUP support was also added to summit which allows
reloading the config at runtime so build_sizes can be updated
w/out having to restart summit.

Most of this commit revolves around removing the
shared `service::Config` as each service should
have its own config so we can easily extend them
& not deal w/ unrepresentable states.

The rest revolves around being able to associate
a `size` to both builders & tasks (recipe names)
so that we can intelligently queue up builds on the
correct sized builder.
@tarkah tarkah force-pushed the task/build-size-config branch from 021cf5f to 5e7860a Compare December 28, 2025 17:29
Copy link
Member

@ermo ermo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been in testing for three weeks now with the DoS fix in place, and is now behaving as expected.

@ermo ermo merged commit 35d1842 into main Jan 5, 2026
2 checks passed
@jplatte jplatte deleted the task/build-size-config branch January 5, 2026 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Summit: Set builder priority + enable recipes to be categorized into large/medium/small builds, phase 1

3 participants