Add manual workflow for cloud integration tests #695
Merged
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
This workflow allows maintainers to manually trigger integration tests that normally only run on the main branch. It includes options for: - S3 integration tests (AWS) - Google Cloud Storage integration tests - Azure Blob Storage integration tests Tests that already run on every push/PR (S3 Mock, SFTP, unit tests, linting) are excluded since they're covered by the commit.yml workflow. The workflow provides flexibility to test cloud storage backends without merging to main, useful for debugging integration issues or testing PRs that affect specific storage implementations. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Remove trailing whitespace - Add newline at end of file 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Add workflow permissions for issues:write and pull-requests:write to enable PR commenting - Create test result directories before uploading artifacts to ensure they always exist - Add try-catch error handling for PR commenting to gracefully handle non-existent PRs - Add continue-on-error to PR comment step to prevent workflow failure These fixes match the improvements made to other workflows and ensure the manual integration test workflow is robust and won't fail due to missing permissions or non-existent artifacts. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
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.
Summary
Test Options
The workflow provides options to run:
Tests that already run on every push/PR (S3 Mock, SFTP, unit tests, linting) are excluded since they're covered by the existing commit.yml workflow.
Access Control
By default, only users with write access to the repository can trigger workflow_dispatch workflows. This includes:
No additional configuration is needed to restrict this to maintainers only.
How to Use
Test plan
Once merged:
🤖 Generated with Claude Code