break apart github actions jobs to save disk space#894
Open
AdamKing0126 wants to merge 3 commits intomainfrom
Open
break apart github actions jobs to save disk space#894AdamKing0126 wants to merge 3 commits intomainfrom
AdamKing0126 wants to merge 3 commits intomainfrom
Conversation
AdamKing0126
changed the title
nicksayre
approved these changes
Dec 19, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The Github Action checks out the
vagov-content,content-build, andvets-websiterepos. This is possibly why we are seeing the actions failing with a failure that there's no space left on the device.The filesystem is preserved between steps in a GitHub Actions workflow. This means that files and directories created in one step are available in subsequent steps. However, the total amount of disk space available in the runner environment is limited. Because we have one action which both fetches the cache and does a
yarn install, it's likely this is running against the boundaries for the amount of disk space available.By splitting this command:
cd content-build && cp .env.example .env && yarn --frozen-lockfile --prefer-offline && yarn fetch-drupal-cache && yarn build...into three separate chunks:
cd content-build && cp .env.example .env && yarn --frozen-lockfile --prefer-offlinecd content-build && yarn fetch-drupal-cachecd content-build && yarn buildWe should avoid this problem