You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am setting up a Jenkins pipeline.
The unit tests are executed with -ojunit to be processed by the Junit tool.
Once the tests failures are coming back to Github Checks, all the newlines are removed.
I can see it is supposed to be {newline}. Is there one config I forgot to allow Jenkins to replace that newline? Is it part of Junit standard?
In the meantime I am building the tests with a local version encoding \n and \r to the encoded equivalent instead of {newline}. AlexisTM@8d90f3f
The text was updated successfully, but these errors were encountered:
Hi, I am setting up a Jenkins pipeline.
The unit tests are executed with
-ojunit
to be processed by the Junit tool.Once the tests failures are coming back to Github Checks, all the newlines are removed.
I can see it is supposed to be {newline}. Is there one config I forgot to allow Jenkins to replace that newline? Is it part of Junit standard?
In the meantime I am building the tests with a local version encoding \n and \r to the encoded equivalent instead of
{newline}
.AlexisTM@8d90f3f
The text was updated successfully, but these errors were encountered: