Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upload CI test results to S3 #23457

Merged
merged 1 commit into from
Sep 23, 2024
Merged

Conversation

nineinchnick
Copy link
Member

Description

Upload CI test results to S3, so we can create reports aggregating most commont failure causes in https://github.com/trinodb/reports.

This will require setting up new vars and secrets with the S3 bucket name and credentials. We can reuse the same bucket where we already copy GHA REST API data scraped in https://github.com/trinodb/reports.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

@cla-bot cla-bot bot added the cla-signed label Sep 17, 2024
@nineinchnick
Copy link
Member Author

I've tested the xml to json conversion in a private Trino fork. That's how I came up with the length limits, since I already tried processing this with Trino.

.github/workflows/ci.yml Outdated Show resolved Hide resolved
Copy link
Member

@electrum electrum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great!

@nineinchnick
Copy link
Member Author

It's ready to be merged, tested in my own fork: https://github.com/nineinchnick/trino/actions/runs/10920342447/job/30309980955

@martint martint merged commit 987311a into trinodb:master Sep 23, 2024
94 checks passed
@github-actions github-actions bot added this to the 459 milestone Sep 23, 2024
@nineinchnick nineinchnick deleted the test-results-to-s3 branch September 24, 2024 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants