action: test-docs workflow should create basic junit report - #1767
Merged
Conversation
otherwise, the test-reporter will fail as no artifacts can be found
reakaleek
approved these changes
Mar 6, 2023
beniwohli
approved these changes
Mar 6, 2023
beniwohli
left a comment
beniwohli
left a comment
Contributor
There was a problem hiding this comment.
Nice workaround! Thanks for the super speedy fix!
v1v
commented
Mar 6, 2023
Closed
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.
What does this pull request do?
Generate junit test report file with a skipped entry for the
test-docsWhy
otherwise, the test-reporter will fail as no artifacts can be found
Issue
elastic/apm-pipeline-library#2121 is the one testing this in isolation.
See https://github.com/elastic/apm-pipeline-library/runs/11788165082