CI: add reusable cleanup workflow #122
Merged
+88
−4
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
ViktorT-11
force-pushed
the
2025-12-add-CI-clenaup
branch
3 times, most recently
from
35ceaab to
384d456
Compare
Define composite actions to remove large toolsets, unused packages, Docker images, and caches from the GitHub runner, freeing up disk space for builds. Note that the content of the cleanup-space/actions.yaml file is copied from the following `tapd` PR: lightninglabs/taproot-assets#1878 There's one distinct difference from the `tapd` file. In this repo, we separate the cleanup of the android folder into a separate action. The reason for this separation is that we need to be able to control when the android folder is cleaned up, during the job, as some jobs will fail if the android folder is removed in the beginning of the job. Not all of the targeted files when running the script, should ever have been used when building the binaries for LNC, but we keep the script consistent between the repos for simplicity.
Update workflows to use the new `cleanup-space` composite action for clearing runner disk space. Note that in the "build package and wasm" job, the cleanup of the android build folder is done after the rest of the step is completed, as the contents of the folder are needed during the "android compile" step.
ViktorT-11
force-pushed
the
2025-12-add-CI-clenaup
branch
2 times, most recently
from
58857b4 to
4bff749
Compare
ffranr
approved these changes
Dec 12, 2025
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.
This PR mimics the PRs from lightningnetwork/lnd#10306 & lightninglabs/taproot-assets#1878, but for LNC, to combat the "no space left on device" issue we've seen in #121.
Note that there's one distinct difference from the
tapdimplementation. In this repo, we separate the cleanup of the android folder into a separate action. The reason for this separation is that we need to be able to control when the android folder is cleaned up, during the job, as some jobs will fail if the android folder is removed in the beginning of the job.