Update build CI to free runner disk space prior to container pull. #89
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
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.
#87 did not quite work as expected, as the job step to free runner disk space ran after the container was pulled (and also erroneously inside the container). This PR replaces the
containertag usage in the workflow with explicitdocker runcommands to ensure the container pull happens after disk space is freed up.Annoyingly, the
issue_commentworkflow trigger only works for workflow files committed tomain(see: https://github.com/orgs/community/discussions/59389), so I merged that PR to test the comment workflow trigger before discovering this other issue. Apologies for the churn.