Background

We wanted to continue to use Ibutsu for test reporting, but we also want to use the external konflux cluster.  External Konflux can't reach Ibustu, but it CAN reach an external mirror of Report Portal.  The other option we had was to use internal konflux, but that would mean we would have to make our repos private, and we rather not do that.  SO we've decided to use Data Router Task, which is officially Konflux-supported, to upload component test reports to Report Portal.  

Details

Konflux team released Data Router Task for Integration Pipelines.

"The Data Router task sends test results and metadata to configured target systems through the Data Router API."

Original announcement with further details: https://groups.google.com/a/redhat.com/g/konflux-announce/c/1PPcMNY9u3M/m/tMByhntgDAAJ

Evaluate if it can suits our needs of test reporting.

External URL for datarouter: https://datarouter.ccitredhat.com/ 

We should assess its ability to provide a smoother test reporting experience.

There are no real usage examples (https://github.com/search?q=org%3ARedHatInsights%20value%3A%20tasks%2Ftest-results%2Fdatarouter%2F0.1%2Fdatarouter.yaml&type=code).

The user guide is here. The Slack channel for support is this.

Acceptance Criteria:

• Evaluate lburnett's proposed ADR and update/comment with findings
  • Support tickets counts in the final evaluation.
• Demo swatch-producer-azure pipeline where test report is uploaded through new task.
  • Using external konflux cluster
• Konflux admin group (internal to swatch) has clarity and alignment.
• If the approach is positive, create new card(s) for adapting the remainder of the existing pipelines