ci: make it easier to find the connector test report url upon failure

[aaronsteers]

Summary by CodeRabbit

• New Features

  • Improved error handling in connector testing workflow with clearer failure messages.
  • Added a link to the execution report for detailed test results.

• Bug Fixes

  • Enhanced output reporting for test failures to improve user clarity.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the .github/workflows/connector-tests.yml file, focusing on improving error handling and output reporting during connector testing. Key changes include a revised error message in the Evaluate Test step, which now provides a more concise indication of test failures and includes a link to the execution report. The Abort if extra not changed step remains unchanged, preserving the workflow's structure and logic for detecting relevant changes in Airbyte connectors.

Changes

File	Change Summary
.github/workflows/connector-tests.yml	- Updated error message in Evaluate Test step for clarity. - Added link to execution report on test failure. - Retained logic in Abort if extra not changed step.

Possibly related PRs

• ci: run airbyte connector tests from master branch #99: Modifies the .github/workflows/connector-tests.yml file to adjust the logic for running connector tests based on codebase changes.
• ci: skip downstream connector tests if no source code is changed #101: Updates the .github/workflows/connector-tests.yml file to enhance job execution control flow based on source code changes.
• ci: reorder job steps #102: Changes the .github/workflows/connector-tests.yml file specifically in job steps, relating to the output reporting improvements.
• ci: update connector-tests.yml worfklow to use dev binary of airbyte-ci #131: Enhances the connector testing process in the .github/workflows/connector-tests.yml file, directly related to this PR's modifications.
• ci: fix CI reports not uploading #138: Improves the reporting capabilities in the .github/workflows/connector-tests.yml file, aligning with the changes made in this PR.

Suggested labels

ci

Suggested reviewers

• alafanechere
• bnchrch

What do you think about the suggested reviewers? Do they seem like a good fit for this PR?

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

.github/workflows/connector-tests.yml (2)

166-168: Consider adding the report URL to the error message, wdyt?

The error message is now more concise, which is great! 🎯 To make it even more helpful, we could include the report URL directly in the error message. This would make it immediately visible in the GitHub UI when the error occurs.

-            echo "::error::Test failed for connector '${{ matrix.connector }}' on step '${failed_step}'. "
+            echo "::error::Test failed for connector '${{ matrix.connector }}' on step '${failed_step}'. See report: ${html_report_url}"

---

169-169: How about adding the report URL to the step summary for better visibility?

The report URL is now included in the logs, but it might be more visible if we also add it to the step summary. GitHub displays step summaries prominently in the UI, making them easier to find. 🔍

           echo "See the execution report for details: ${html_report_url}"
+          echo "## Test Report" >> $GITHUB_STEP_SUMMARY
+          echo "📊 [View detailed test report](${html_report_url})" >> $GITHUB_STEP_SUMMARY

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0f40e22 and 09edf60.

📒 Files selected for processing (1)

• .github/workflows/connector-tests.yml (1 hunks)