Optimize Build Pipeline Disk Space #51
Open
Conversation
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
magajh
reviewed
Jan 16, 2026
| ssh-key: ${{ inputs.STRAIN_REPOSITORY != github.repository && secrets.SSH_PRIVATE_KEY || '' }} | ||
| path: strains | ||
|
|
||
| - name: Clean Up Disk Space |
Contributor
There was a problem hiding this comment.
Good catch @DeimerM. I’m aligned with this change, and I don’t think the added build time (under 2 minutes) is a major concern
It would be nice to expose this as a configurable flag, maybe we can leave the default to true (enable disk space cleanup), while allowing it to be disabled for environments where it’s not required (e.g., larger runners) to reduce build time
Please let's make sure this option is documented in the README
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR adds a specialized cleanup step to the image build pipeline. It is designed to remove default resources and pre-installed software provided by the GitHub Actions (GA) runners that are not necessary for our specific build process.
Why is this necessary?
We have encountered no space left on device errors (specifically during the #111 importing to docker stage) because the standard GitHub-hosted runners have a limited disk capacity (approx. 14GB–18GB). Large Docker builds—especially those involving heavy node_modules or multiple layers—can exceed this limit.
By clearing out unused tools like the Android SDK, .NET, and the hosted tool cache, we can reclaim up to 20GB+ of additional disk space for the build process.