mvn clean compile test xray:import-results - code 400 #86
Replies: 2 comments 5 replies
-
Hi @fredericMagnenat ,
Something like curl -H "Content-Type: multipart/form-data" -u admin:admin -F "[email protected]" "http://yourserver/rest/raven/2.0/import/execution/junit?projectKey=XTP"
mvn clean compile test xray:import-results -Dxray.verbose=true -X |
Beta Was this translation helpful? Give feedback.
-
As per your logs, it seems you are referring to a issue in Jira that is not valid: WACO-5. Can you check that? Is it a Test issue or a Test Execution issue? It would also help out if you could share the JUnit XML file. " {"error":"WACO-5 n\u0027est pas un ticket d\u0027exigence ou n\u0027est pas une clé de ticket valide."}"´ Anyway, it doesnt seem to be an issue of this plugin but more a usage related thing. |
Beta Was this translation helpful? Give feedback.
-
Hey,
I am using the xray-maven-plugin version 0.8.0 to import JUnit test results into Jira Xray. However, I have noticed that the plugin is calling an outdated API endpoint.
Currently, the plugin uses rest/raven/2.0/import/execution/junit?projectKey=XXX, but Xray's documentation recommends using the newer endpoint: rest/raven/2.0/api/import
The plugin doesn’t seem to provide a way to configure the endpoint to use this new API path. I would like to know how to resolve this issue or if there’s a way to customize the API URL in the plugin’s configuration.
Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions