Ability to support AWS S3 coverage sync. #39
Merged
+145,744
−1,981
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.
Add S3 Integration for Coverage Report Management
Changes
s3-repo-directory
Features
s3-repo-directory
to organize multiple repos in one bucketConfiguration
New parameters added:
aws-access-key-id
: AWS access key for S3 operationsaws-secret-access-key
: AWS secret key for S3 operationsaws-region
: AWS region (defaults to 'us-east-2')s3-bucket
: S3 bucket names3-repo-directory
: Optional directory for organizing multiple reposbase-branch
: Base branch name (defaults to 'main')s3-base-url
: Optional base URL for S3 coverage reportsTesting
Impact
This change significantly simplifies coverage report management by:
Screenshots
N/A - Backend changes only
Related Issues
N/A