GCS Integration Tests Migration to Github Worfklow#4
Merged
ramonskie merged 7 commits intocloudfoundry:mainfrom Nov 19, 2025
Merged
Conversation
- setup, run and teardown steps separated. - Makefile updated
- README updated; How to run integration and unit tests content changed.
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.
Context
The integration tests previously ran in a Concourse pipeline. As part of consolidating all clis into storage-cli repository, the Concourse pipelines needed to be fully migrated to GitHub Workflows.
Solution
A new GitHub Workflow has been introduced. The existing Concourse test logic and helper scripts were carried over where appropriate. The workflow includes two jobs, gcs-integration-fast-tests and gcs-integration-all-tests, matching the structure used in the Concourse pipeline.
Each job creates the required GCS buckets dynamically during execution and cleans them up afterward.
All credentials needed for provisioning these resources are stored under the gcs-integration secret group in GitHub.