You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent changes as part of the v0.17.0 release the space required to build all images has exceeded the space provided by the "Standard" GitHub-hosted runners (for Public repositories).
To work within those constraints we'll need to break up the image generation & upload steps. This should (by my current understanding) allow the total build & upload tasks to be split into batches across separate runners.
Keep existing `build` and `upload` recipes as aliases for the
total recipes of that type.
CI jobs have not been updated yet. If this passes CI tasks
(which would prove that at least the build tasks haven't been
broken) I'll update the CI workflow next to use the batch
build/upload tasks.
refs GH-1451
Switch workflow from a monolithic build/upload approach to
separate build/upload jobs based on image grouping:
- mirror images
- alpine images
- mingw-64 images
- standard images
This is intended to avoid hitting per-runner disk space limits
but *may* also result in a significant observed runtime decrease.
refs GH-1451
atc0005
changed the title
Building all images has exceeded "Standard" GitHub-hosted runners disk space
Building all images exceeds "Standard" GitHub-hosted runners disk space
Mar 23, 2024
Switch workflow from a monolithic build approach to
separate build jobs based on image grouping:
- mirror images
- alpine images
- mingw-64 images
- standard images
This is intended to avoid hitting per-runner disk space limits.
refs GH-1451
Switch workflow from a monolithic build approach to
separate build jobs based on image grouping:
- mirror images
- alpine images
- mingw-64 images
- standard images
This is intended to avoid hitting per-runner disk space limits.
refs GH-1451
Remove settings specific to the release builds workflow which
do not apply to the monthly schedule tasks workflow (lack of
upload task and need for token/perms).
refs GH-1465
refs GH-1451
Overview
With the recent changes as part of the v0.17.0 release the space required to build all images has exceeded the space provided by the "Standard" GitHub-hosted runners (for Public repositories).
To work within those constraints we'll need to break up the image generation & upload steps. This should (by my current understanding) allow the total build & upload tasks to be split into batches across separate runners.
References
The text was updated successfully, but these errors were encountered: