We implemented test report upload through Data Router.

For achieving that we used a deprecated way to pass XML report from tests execution to tests upload step.

We utilized PVC (Persistent Volume Claim) in the form of workspace. This approach is ok if the artifact produced (test reports in this case) is shared among the same task, but the Konflux team is not suggesting it with workflows that spans among tasks (a confirm from the Konflux team would be great).

In our case we wrapped data router in a custom script and skipped the OCI artifact upload on Quay overall.

We want to be compliant with Konflux directives and pass artifacts to Quay, before uploading them in Report Portal.

This requires an team-wide account able to push and pull artifacts to a shared public repo dedicated to that. Ref. https://source.redhat.com/departments/products_and_global_engineering/cee_customer_service/for_non_cs_associates_wiki/how_to_request_a_quay_employee_subscription

Once we got the OCI credentials, we can set up a full-fledged Data Router task without the need of a custom wrapper.

Slack Data Router channel: https://redhat.enterprise.slack.com/archives/C06Q4M84XDG

Acceptance Criteria:

• We have team-wide and available user for uploading test reports to Quay.
  • The credentials should be stored in Vault and referenced in Konflux as ExternalSecrets.
• Use the latest version of Data Router Task in component test pipeline.
• The test reports are uploaded correct to Report Portal.
• There is a way to retry if the upload is not successful.