-
Notifications
You must be signed in to change notification settings - Fork 5
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
ci: fix CI reports not uploading #138
Conversation
/autofix
|
📝 Walkthrough📝 WalkthroughWalkthroughThe pull request modifies the Changes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
.github/workflows/connector-tests.yml (1)
136-138
: Consider parameterizing the bucket name? 🤔The hardcoded bucket name works, but would it be more flexible to move this to a GitHub secret or environment variable? This would make it easier to use different buckets for different environments, wdyt?
- --ci-report-bucket-name=airbyte-ci-reports-multi \ + --ci-report-bucket-name=${{ secrets.CI_REPORT_BUCKET_NAME }} \
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
.github/workflows/connector-tests.yml
(5 hunks)
🔇 Additional comments (2)
.github/workflows/connector-tests.yml (2)
97-98
: LGTM! The checks permission is necessary.
The addition of checks: write
permission is appropriate for creating check runs and aligns with the goal of improving report accessibility.
Line range hint 146-170
: Great job on the enhanced reporting! 👏
The changes nicely improve the visibility of test results by:
- Extracting and displaying the HTML report URL
- Adding clear success/failure indicators
- Providing structured outputs for downstream steps
This aligns perfectly with the PR's goal of making reports more accessible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also make the GH check line link to the html report?
Approving contingent on the comment that you made to revert the thing to master
@natikgadzhi - Yes, I think so. I wanted to implement the same but my attempt was reverted here (a50c1b7) due to a "not found" error when I tested it. I'll create a follow-on issue to try again in another PR... Update: logged here: |
This resolves the issue where
airbyte-ci
reports were not being uploaded, and the PR author would have to manually download the job results artifact, then decompress, and then navigate to the report url.Requires this PR to be merged:
--is-ci
flag to upload reports to GCS bucket airbyte#48824Now, the report URL is printed in the job execution log (as usual for Airbyte CI tests):
For convenient access, it is also posted to the "Summary" page of the GitHub Workflow for easy access, and to prevent having to scan through job logs:
https://github.com/airbytehq/airbyte-python-cdk/actions/runs/12187332389?pr=138
The job artifacts are still downloadable from the bottom of the Summary page as well, in case other test report artifacts are useful - but for most cases, you can simply go to the summary page and click on the report link in the job summary.
Summary by CodeRabbit
New Features
Bug Fixes
Chores