feat(STONEINTG-999): report test status for group snapshot

[hongweiliu17]

• update template to generate text reported to git provider
• report test status for group snapshot

Signed-off-by: Hongwei Liu hongliu@redhat.com

Maintainers will complete the following section

• Commit messages are descriptive enough (hints)
• Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
• Controllers diagrams are updated when PR changes controllers code (if applicable)

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 60.56338% with 56 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@1fa734b). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
...al/controller/statusreport/statusreport_adapter.go	56.32%	26 Missing and 12 partials ⚠️
status/status.go	74.35%	7 Missing and 3 partials ⚠️
gitops/snapshot.go	42.85%	4 Missing and 4 partials ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #860   +/-   ##
=======================================
  Coverage        ?   69.24%           
=======================================
  Files           ?       43           
  Lines           ?     4552           
  Branches        ?        0           
=======================================
  Hits            ?     3152           
  Misses          ?     1062           
  Partials        ?      338           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hongweiliu17]

The new text template with component snapshot info for group snapshot can generate content like below:

Pipelinerun: pipelinerun-component-sample

---

Task	Duration	Test Suite	Status	Details
example-task-1	5m30s	example-namespace-1	✔️ SUCCESS	✔️ 2 success(es) ⚠️ 1 warning(s)
example-task-2	2m0s		✔️ Reason: Succeeded	✔️ Reason: Succeeded
example-task-31	1s	example-namespace-3	❌ FAILURE	❌ 1 failure(s)
example-task-42	1s	example-namespace-4	⚠️ WARNING	⚠️ 1 warning(s)
example-task-5	5m0s	example-namespace-5	✅ SKIPPED
example-task-6	1s	example-namespace-6	❗ ERROR

The group snapshot is generated for the component snasphots as below:

Component	Snapshot	BuildPipelineRun
com1	snapshot1	buildPLR1
com2	snapshot2	buildPLR2
com3	snapshot3	buildPLR3

Footnotes

1. example note 3 ↩

2. example note 4 ↩

[hongweiliu17]

The feature code is ready for review. I will work on the unit test part next.

[dirgim]

LGTM

[chipspeak]

LGTM Inspirational stuff as always Hongwei!

[hongweiliu17]

Test on my personal cluster and it can create checkRun successfully, refer to https://github.com/hongweiliu17/devfile-sample-go-basic-1772/pull/1/checks?check_run_id=30507639589 and https://github.com/hongweiliu17/devfile-sample-java-springboot-basic-1772/pull/1/checks?check_run_id=30507642618

[openshift-ci]

New changes are detected. LGTM label has been removed.

[hongweiliu17]

Found one bug in when SetLastUpdateTime, because this is a loop, so we may need to also include the componentName in https://github.com/konflux-ci/integration-service/blob/main/status/status.go#L48. To make the review easier, I prefer to merge this PR then commit another PR to fix it.

[hongweiliu17]

/retest

[hongweiliu17]

/retest

[hongweiliu17]

/retest-required

[hongweiliu17]

/retest

[dirgim]

/retest

[flacatus]

/retest

[flacatus]

/retest

[flacatus]

/retest