[FLINK-39884][ci] Run free_disk_space.sh in the GitHub Actions e2e jobs#28375
Merged
Conversation
Ports the Azure Pipelines disk cleanup to GitHub Actions. The e2e jobs run directly on the ubuntu-24.04 runner (not in a container), where the e2e tests download and generate more than 17GB of files. The existing job_init cleanup only removed the Android SDK, CodeQL and .NET; the free_disk_space.sh script frees roughly 34GB on the same runner image. The script is opt-in via a new job_init input because the compile and test jobs run inside the CI container, where the runner's disk cannot be cleaned up. Generated-by: Claude Code (Fable 5)
Collaborator
snuyanzin
approved these changes
Jun 11, 2026
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
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.
What is the purpose of the change
Follow-up to FLINK-39884, which extended
tools/azure-pipelines/free_disk_space.shto free roughly 34GB on the CI machines. That cleanup so far only runs on Azure; the GitHub Actionsjob_initaction only removes the Android SDK, CodeQL and .NET.The GHA e2e jobs run directly on the ubuntu-24.04 runner (not in the CI container) and download/generate more than 17GB of files, so they benefit from the same cleanup as the Azure e2e jobs on the identical runner image.
Brief change log
free_disk_spaceinput to.github/actions/job_initthat runstools/azure-pipelines/free_disk_space.shinstead of the smaller inline cleanup.github/workflows/template.flink-ci.ymlThe input is opt-in because the compile/packaging/test jobs run inside the CI container, where the runner's disk cannot be cleaned up (the existing inline cleanup remains in place for them).
Verifying this change
This change is a CI configuration change without test coverage. The existing
df -hsteps before/afterjob_initwill show the reclaimed space (~30GB expected) in the e2e job logs of the next runs. The script preserves/opt/hostedtoolcache/Pythonand the JDKs under/usr/lib/jvm, which the subsequentsetup-pythonandJAVA_HOME_<version>_X64steps rely on; the Docker image prune happens before the e2e job loads its cached testcontainers images.Does this pull request potentially affect one of the following parts:
@Public(Evolving): noDocumentation
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5)