-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
-
3.1.0
The junit pipeline step in the JUnit plugin publishes checks to Checks API since https://github.com/jenkinsci/junit-plugin/pull/180. I'd like a similar feature in the xunit pipeline step in the xUnit plugin.
[JENKINS-64714] Publish test results from xUnit Plugin to Checks API
Kalle Niemitalo
added a comment - This feature is disabled by default in 3.1.0. That's OK, but it is not clear from the documentation.
Kalle Niemitalo
added a comment - This feature is disabled by default in 3.1.0. That's OK, but it is not clear from the documentation. Kalle Niemitalo
added a comment - Okay, I was able to use this with a private plugin (https://github.com/jenkinsci/checks-api-plugin/issues/65) to publish the numbers of successful and skipped tests to Bitbucket Server. Caveats:
- The Markdown description cannot get through, until Atlassian implements [BSERV-11523] Support markdown in code insight reports.
- The xUnit plugin generates a checks name that contains spaces and slashes. Bitbucket Server does not allow this name and returns HTTP status 400. So the name has to be overridden using withChecks.
Kalle Niemitalo
added a comment - Okay, I was able to use this with a private plugin ( https://github.com/jenkinsci/checks-api-plugin/issues/65 ) to publish the numbers of successful and skipped tests to Bitbucket Server. Caveats:
The Markdown description cannot get through, until Atlassian implements [BSERV-11523] Support markdown in code insight reports .
The xUnit plugin generates a checks name that contains spaces and slashes. Bitbucket Server does not allow this name and returns HTTP status 400. So the name has to be overridden using withChecks .
Apparently implemented in https://github.com/jenkinsci/xunit-plugin/pull/96 and manually merged in https://github.com/jenkinsci/xunit-plugin/commit/66e06d2d02e9d32212aec8f853d56b71f6f04d99.