Skip to content

Suggested Changes To Support Access To Test Results By Downstream Consumers#72

Open
GaryBurgin wants to merge 1 commit intomuselab-d2x:mainfrom
GaryBurgin:patch-1
Open

Suggested Changes To Support Access To Test Results By Downstream Consumers#72
GaryBurgin wants to merge 1 commit intomuselab-d2x:mainfrom
GaryBurgin:patch-1

Conversation

@GaryBurgin
Copy link
Copy Markdown

  • The ci_feature_2gp flow runs run_tests, which produces test_results.json and test_results.xml by default
  • These files are currently lost when the job completes — no downstream consumers can access them
  • Uploading them as artifacts enables consuming workflows (via workflow_run trigger) to download and report on results (e.g., PR comments, badge generation)
  • retention-days: 7 keeps storage costs minimal
  • if-no-files-found: warn avoids failing the job if tests were skipped

Another alternative would be to create a custom fork of this flow and modify it, is this what you would recommend or is the above a reasonable approach?

…ctions

- The ci_feature_2gp flow runs run_tests, which produces test_results.json and test_results.xml by default
- These files are currently lost when the job completes — no downstream consumers can access them
- Uploading them as artifacts enables consuming workflows (via workflow_run trigger) to download and report on results (e.g., PR comments, badge generation)
- retention-days: 7 keeps storage costs minimal
- if-no-files-found: warn avoids failing the job if tests were skipped
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant