With GitHub Actions we can implement complete CI/CD workflows. But is there a way to display test, code coverage, and miscellaneous reports in a friendly HTML format like Jenkins and other CI/CD platforms?
Or is it recommended to offload testing to another platform (e.g. Jenkins, Circle CI, etc.)?
What about artifact management?
Solved! Solved! Go to Solution.
GitHub Actions is intended to be very open-ended to allow you to implement whatever kind of workflow you can imagine. In order to be this open-ended though, that means that whoever implements the Actions in the workflow will have to build the code, components, or whatever other infrastructure is necessary to display the reports that you're describing. So the workflow can execute the task of running tests, executing code coverage, collecting their reports, and uploading them to a host somewhere they can be referred back to later. But that hosting will have to be somewhere outside of the workflow since a workflow is time-limited. The same is true for build artifact management.
I hope that helps!