Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins test result report broken after upgrading to v6 #74

Closed
nicolasschabram opened this issue Jan 11, 2019 · 5 comments
Closed

Jenkins test result report broken after upgrading to v6 #74

nicolasschabram opened this issue Jan 11, 2019 · 5 comments
Labels

Comments

@nicolasschabram
Copy link

nicolasschabram commented Jan 11, 2019

After upgrading to v6, Jenkins/xUnit fail to read the test result reports (complaining about the file attribute in testcase):

WARNING: At line 3 of file:/var/lib/jenkins/workspace/[...]/target/junit.xml:cvc-complex-type.3.2.2: Attribut 'file' darf nicht in Element 'testcase' vorkommen.
[...]
FATAL: The result file '/var/lib/jenkins/workspace/[...]/target/junit.xml' for the metric 'JUnit' is not valid. The result file has been skipped.

I guess it has to do with #71.

Anyone else experiencing this problem?


Jenkins: v2.150.1
xUnit plugin: v.2.3.2

@palmerj3 palmerj3 added the bug label Jan 11, 2019
@palmerj3
Copy link
Collaborator

@nicolasschabram thanks for reporting. I may roll back that change if it's broken on jenkins. For now please use v5 but I'm going to leave this issue open for a bit to see if others hit this problem.

@palmerj3
Copy link
Collaborator

Hey @nicolasschabram I have rolled back this change and published 6.0.1. Would you please test out this version on your pipeline and let me know if it works?

@nicolasschabram
Copy link
Author

It does, thank you very much! @palmerj3

@palmerj3
Copy link
Collaborator

@nicolasschabram cool I will close this. If you don't mind I will ping you in the next few days when we re-add this functionality as a configuration option. It's always useful if I have some folks that can test it in their environment.

@nicolasschabram
Copy link
Author

Sure, happy to help! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants