Use ubuntu-latest runners for Apache Beam and Spring Boot experiments
#108
Conversation
This file contains 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
runningcode
approved these changes
Jul 12, 2024
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.
In January, GitHub bumped the specs of the default runners:
Both Apache Beam and Spring Boot are using paid-for runners with the exact specifications as the standard runners. However, the standard runners quickly run out of disk space. Both builds were failing due to insufficient disk space in my initial testing.
I did some digging and discovered the Spring Boot project recently switched to using
ubuntu-latest. I noticed they introduced this jlumbroso/free-disk-space action as part of those changes.I tried using this same action and both the Beam and Boot experiments finished successfully.
This PR reverts both Apache Beam and Spring Boot to using the standard runners