Encode newlines for -ojunit as their XML equivalent instead of {newline} #1598
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
|
Some test is still missing. I'll add it myself in another PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When calling the tests with
-ojunit(Junit output),\nare replaced by{newline}which causes the Github Checks output to be inlined.This PR is replacing
\nand\rby their encoded equivalent respectively and .Now, when Jenkins reports the tests to Github Checks, the tests failures are readable.
What is the reason we are not replacing
\nby{newline}? Should this instead be a Jenkins Junit plugin update to support{newline}or a post process from the user in the Jenkins pipeline?Closes #1594