search

Xray-App / xray-maven-plugin

Xray Maven Plugin
BSD 3-Clause "New" or "Revised" License
26 stars 12 forks source link

issue with linking to Test Plan #48

Closed iclman closed 2 years ago

iclman commented 2 years ago

Hello;

Version of plugin used: 0.6.0 (https://repo1.maven.org/maven2/app/getxray/xray-maven-plugin/0.6.0/) Version of Jira used: v8.20.8 Version of mvn used : 3.6.0

Command maven: mvn -gs my-global-settings.xml xray:import-results -Dmaven.repo.local=/mytmp/maven-repositories -Dxray.jiraToken=**** -Dxray.jiraBaseUrl=https://myjira.server/ -Dxray.projectKey=ORI2 -Dxray.testPlanKey=ORI2-791 -Dxray.cloud=false -Dxray.reportFormat=junit -Dxray.reportFile=/mytmp/myresults.xml

The test executions tickets are created correctly in Jira However, the links to the test plan ORI2-791 are not created.

Have you already encountered that kind of issue or did I forget something ?

Thanks

bitcoder commented 2 years ago

Can you please try to upload the results using curl tool directly, or other similar one, using the junit standard endpoint (https://docs.getxray.app/display/XRAY/Import+Execution+Results+-+REST) and see if that works?

(please update login/pass in the following request example)

curl -H "Content-Type: multipart/form-data" -u admin:admin -F "file=@/mytmp/myresults.xml" http://yourserver/rest/raven/2.0/import/execution/junit?projectKey=ORI2&testPlanKey=ORI2-791"

bitcoder commented 2 years ago

I confirm it's a bug

bitcoder commented 2 years ago

for Xray DC/server, only projectKey was being passed. testPlanKey, testExecKey, revision, fixVersion http arguments were not being passed. besides, testEnvironment should be passed as testEnvironments on the HTTP request

iclman commented 2 years ago

Thanks for the update. Is there any plan to perform these fix or evolution on DC/server in the near future ?

bitcoder commented 2 years ago

Today 😀

bitcoder commented 2 years ago

fixed in version 0.7.0