Expose JUnit test report for Bazel #96
Closed
Conversation
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
srueg
force-pushed
the
srueg/junit-test-report
branch
from
bf4aac6 to
d9224a8
Compare
Use the `$XML_OUTPUT_FILE` env var to expose the generated JUnit report to Bazel [1]. [1]: https://bazel.build/reference/test-encyclopedia#initial-conditions
srueg
force-pushed
the
srueg/junit-test-report
branch
from
d9224a8 to
96f2648
Compare
|
Better approach in #93 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use the
$XML_OUTPUT_FILEenv var to expose the generated JUnit report to Bazel 1.