Containerize GCSFuse integration tests #4125
Draft
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 introduces a Dockerized workflow for running GCSFuse integration tests. It addresses the need for a consistent, isolated testing environment while maintaining access to GCP credentials and the current source code state.
Key changes:
tools/integration_tests/container/Dockerfile: Defines the test environment. Crucially, it patches the existingimproved_run_e2e_tests.shscript inside the container to bypass theinstall_packagesfunction, as the Dockerfile ensures all dependencies are pre-installed. This avoids modifying the source script in the repository.tools/integration_tests/container/run_e2e_docker.sh: A convenience script to build and run the container with the correct flags and mounts.PR created automatically by Jules for task 13503203724161362538 started by @kislaykishore