-
Notifications
You must be signed in to change notification settings - Fork 460
feat(orchestrator): make build-reserved-disk-space-mb default 256MB #3065
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c8a1adf
feat(orchestrator): make build-reserved-disk-space-mb default 256MB
arkamar fc83feb
test(integration): bump seeded base build disk to 1024MB
arkamar cb71c35
test(integration): bump seeded base build disk to 2048MB
arkamar 73f489c
test(integration): build CI base template with larger disk
arkamar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this fallback now reserving 256 MB for every local/offline build, API-triggered integration template builds still use the integration team's base
disk_mblimit of 512 becauseRegisterBuildsendsdata.Team.Limits.DiskMbto template-manager and the seed addon only increases concurrency, notextra_disk_mb. The updatedenv_buildsrows only affect the already-seeded template, so disk-heavy integration builds created through/v3/templatesstill lose half their writable space before RUN steps and can fail despite the intended 1024 MB bump.Useful? React with 👍 / 👎.