Need clarification on GitHub Actions

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?

Good question!

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!

2 Likes

FTR you can achieve some of that by posting Markdown via Checks API. I guess you could try embedding images as base64-encoded data-urls…

I don’t see GitHub actions on my GitHub repositories.

https://github.com/gitthermal/thermal

@mittalyashu You have to sign up for beta access first.

1 Like

I guess that is a posh way of confirming that there is no support for hosting any build artifacts. The fact that there is an action to create a zip file does not bring much value, we were already able to do the same using curl or whatever tool we wanted.

Still, ability to browse build artifacts, like html reports is a very basic functionality for any CI/CD tool. A zip file is anything but user friendly, as it would require user to download the file, unzip it in order to look at it. Should I also mention that sharing links to a report now becomes sharing links to a zip file… hmm. I doubt many people would find “zip” approach as being practical, unless you really produce binaries.

1 Like

I agree with @ssbarnea

In some of our private repositories, we generate an API documentation as part of the CI process.
Currently, we upload the HTML for the docs along with the test reports as a ZIP, which has to be downloaded, everytime someone wants to look up the latest docs. 

Other CI/CD tools provide this functionality and I think that this would make the GitHub CI/CD workflow a lot more usable.

1 Like