Story (Required)

As a developer trying to use pipelines-as-code and the Dance/RHTAP/Konflux tasks to build and scan my images, I want to see the results of my tests and scans rendered back to my pull request / merge request in detail so that I can take action on those results.

Background (Required)

In https://github.com/redhat-appstudio/architecture/pull/103, Konflux team decided to standardize on TEST_OUTPUT and SCAN_OUTPUT results to store JSON information about test and scan output. This is rendered in the Konflux UI, and will be rendered to the openshift console UI in OCPSTRAT-968.

Developers are often not looking at or using the Konflux UI or OpenShift Console. We pay attention to our pull requests and merge requests. If we could provide that more nuanced result information directly to the github checks API and the gitlab merge request, we would delight developers by surfacing the value provided by scanners and tests.

Out of scope

Seeking broad upstream agreement on results conventions, as in SRVKP-3820.

Approach (Required)

Review details in https://github.com/redhat-appstudio/architecture/pull/103,

Dependencies

None.

Acceptance Criteria (Mandatory)

Konflux and RHTAP (Dance) pipeline results show up in GitHub and Gitlab UIs.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met