Skip to content

🚀 report-portal: Support multiple launch names or show all launches #6613

@nworbiii

Description

@nworbiii

Workspace

report-portal

🔖 Feature description

Support displaying test statistics from multiple ReportPortal launches for a single component. Currently only one launch name can be specified, but many projects have separate launches for different test types (Unit Tests, Integration Tests, API Docs Tests, etc.).

🎤 Context

The current implementation requires both reportportal.io/project-name and reportportal.io/launch-name annotations. The isReportPortalAvailable() function returns false if either is missing, and the filter uses exact matching on a single launch name.

This forces teams to choose one launch type to display, losing visibility into other test results. For example, a project with 550 unit tests, 21 integration tests, and 55 API docs tests can only show one of these in Backstage.

✌️ Possible Implementation

Option A: Support comma-separated launch names

annotations:
  reportportal.io/launch-name: Unit Tests,Integration Tests,API Docs Tests

Option B: Make launch-name optional and show all launches when omitted

Files to modify:

  • plugins/report-portal/src/utils/isReportPortalAvailable.ts
  • plugins/report-portal/src/components/ReportPortalOverviewCard/ReportPortalOverviewCard.tsx

Open questions:

  1. How should the Test Statistics card display multiple launches? (Aggregate totals vs. per-launch breakdown vs. multiple cards)
  2. Where should "View on ReportPortal" link to with multiple launches? (Project launches page vs. multiple links vs. most recent launch)

👀 Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

Yes I am willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions