Add smart-tests-results-upload-action to CI workflows#1344
Merged
Conversation
Integrate cloudbees-oss/smart-tests-results-upload-action@v1 into all three CI workflows so test artifacts are automatically uploaded after each run, including on failure. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
NicuPascu
approved these changes
Jun 18, 2026
ono-max
approved these changes
Jun 18, 2026
gayanW
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Test artifacts (XML reports, etc.) were not being preserved after CI runs, making it difficult to diagnose failures or feed results into Smart Tests analysis.
What
Added
cloudbees-oss/smart-tests-results-upload-action@v1as the final step in all three CI workflows:test.yml— after Python unit tests completebazel-test.yml— after Bazel tests completee2e.yml— after all e2e tests (bazel, go, gradle) completeAll steps use
if: always()so artifacts are uploaded even when tests fail.The action uses its default
filespatterns which cover**/*.xml,**/*.json,**/test-results/**, and more.