Releases: easimon/maximize-build-space
Fix: Build Mount folder Ownership
What's Changed
- fix: if the build mount "deleted" / shadowed the GITHUB_WORKSPACE, do not only recreate it, but also ensure it belongs to the correct owner (
runner
) again
Full Changelog: v9...v10
Allow build mount path to be a parent of $GITHUB_WORKSPACE
This release adds support for mounting the build volume over a parent folder of $GITHUB_WORKSPACE
.
Previously, doing so would remove/shadow the current working directory, and make any later actions/steps fail.
New features:
- Warn about $BUILD_MOUNT_PATH not being empty and list contents in that case
- Recreate
$GITHUB_WORKSPACE
afterwards if missing, so following actions have a working directory to start from.
Ensure mount point directory exists, allow custom ownership
- When using custom mount points, ensure that the specified target directory exists
- Allow changing ownership of mounted volume (specify as
user:group
, defaults torunner:runner
, which is the default github actions user/group)
Thanks to @dawidd6 for the contribution!
Allow removal of docker images and codeql
Adds two more toggles to remove preinstalled docker images and codeql, freeing additional ~8GB.
Thanks to @davidmhewitt for this contribution.
Add MIT LICENSE to repository
No functional changes, just a permissive license.
Change owner GID of mounted volume to runner as well
v5 Change GID in addition to UID for mounted volume
Do not overprovision disk space by default
Added
- Configuration option of overprovisioning the build volume (
overprovision-lvm
), defaulting to'false'
. - Configurable temp volume reserve (
temp-reserve-mb
), defaulting to'100'
.
Changed
- (potentially breaking) The LVM image files are not created sparsely anymore. Previously, free disk space appeared free on both the build volume and the hosting volume, until actually allocated by writing to the build volume. Now, the space is actually consumed on volume creation -- meaning, that after creating the build volume, the root and temp volume do not have or show more space available than configured in
root-reserve-mb
andtemp-reserve-mb
. This can be reverted by settingoverprovision-lvm
to'true'
, but surprising out-of-disk space situations might be the result. - Temp volume reserve was fixed to 1024 KB, this defaults to a more cautious 100 MB now, and is configurable.
Fix running on Ubuntu 20.04
Includes a workaround for the temp disk being locked on Ubuntu 20.04.
The LVM volume is now created ontop of loop-mounted files on both / and /mnt.
Fix file system permissions on logical volume
Changes the owner of the logical volume to the runner user, fixing permission issues when e.g. checking out code to the root of the logical volume.
Actually, the problem is the lost+found
folder in the ext4 root, and chown
ing it breaks its purpose. But since the volume is temporary anyway, lost+found
functionality is not really needed.
Initial release
Initial release