[polarion] Merge xmls with junitparser #1918
Conversation
|
Thanks for the PR! ❤️ |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/80d8eab8c09646b98170eb25305294dd ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 52m 05s |
kopecmartin
force-pushed
the
multiple_xmls
branch
from
04d439c to
9cc97d2
Compare
kopecmartin
changed the title
kopecmartin
force-pushed
the
multiple_xmls
branch
3 times, most recently
from
37ca45a to
8710b05
Compare
In case there are multiple xml files that need to be reported to polarion, we need to merge them before passing them to jump. Using junitparser even in cases where there is only one xml file will have these benefits: * we don't have to write when conditions * the output xml will have the same structure - the content will be wrapped in <testsuites> tags whether we have more xml results or not - testsuite in junitparser context equals to one xml input.
kopecmartin
force-pushed
the
multiple_xmls
branch
from
8710b05 to
a988d52
Compare
|
/lgtm |
|
Just please note in the future we will need to readd the loop, for example when a job reports different "phases" of testing. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: raukadah The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 7527689
into
openstack-k8s-operators:main
In case there are multiple xml files that need to be reported
to polarion, we need to merge them before passing them to jump.
Using junitparser even in cases where there is only one xml file
will have these benefits:
be wrapped in tags whether we have more xml results
or not - testsuite in junitparser context equals to one xml input.
As a pull request owner and reviewers, I checked that: