feat: "rebalance" chunked layer plan once per month#1824
Merged
RoyalOughtness merged 3 commits intosecureblue:livefrom Jan 22, 2026
Merged
feat: "rebalance" chunked layer plan once per month#1824RoyalOughtness merged 3 commits intosecureblue:livefrom
RoyalOughtness merged 3 commits intosecureblue:livefrom
Conversation
HastD
force-pushed
the
clear-build-plan
branch
from
106c720 to
fe486c9
Compare
RoyalOughtness
previously approved these changes
Jan 22, 2026
When taking into account a prior build's layer plan, build-chunked-oci attempts to minimize layer changes between builds. In particular, this means newly added packages are all put in a specific layer reserved for new packages, rather than being distributed among existing layers. This is reasonable behavior but over time can result in an unbalanced, non-optimal package distribution, reducing the effectiveness of rechunking. To mitigate this, we pass `rechunk_clear_plan: true` to the BlueBuild action only on the first build of each month. This strikes a balance: a single update per month being larger has a minimal impact on average update sizes, while preventing the layer plan from remaining unbalanced long-term when the set of installed packages changes. Also update the BlueBuild action to v1.11.0 and remove an option made unnecessary by this update.
HastD
force-pushed
the
clear-build-plan
branch
from
fe486c9 to
d66070d
Compare
RoyalOughtness
approved these changes
Jan 22, 2026
RKNF404
approved these changes
Jan 22, 2026
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
3 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.
When taking into account a prior build's layer plan, build-chunked-oci attempts to minimize layer changes between builds. In particular, this means newly added packages are all put in a specific layer reserved for new packages, rather than being distributed among existing layers. This is reasonable behavior but over time can result in an unbalanced, non-optimal package distribution (especially if a large number of new packages or a large new package is installed), reducing the effectiveness of rechunking.
To mitigate this, we pass
rechunk_clear_plan: trueto the BlueBuild action only on the first build of each month. This strikes a balance: a single update per month being larger has a minimal impact on average update sizes, while preventing the layer plan from remaining unbalanced long-term when the set of installed packages changes.Also update the BlueBuild action to v1.11.0 and remove an option made unnecessary by this update.