uhafner / autograding-github-action Goto Github PK

Hi,

I was looking for a github actions counterpart to the Warnings NG plugin, and this action seems to be pretty close (even when I understand it was made for a different purpose), so I tried it out and I had this strange error when using it without explicit configuration:

No configuration provided (environment CONFIG not set), using default configuration
Can't read configuration: default.conf

This is the workflow run: https://github.com/fwilhe2/spring-petclinic/actions/runs/4983874769/jobs/8921470121

Here is that version of the workflow causing the error: https://github.com/fwilhe2/spring-petclinic/blob/d9f25097ea4a670d2f33dc9d31830ffca6256cba/.github/workflows/maven-build.yml

This can be mitigated by providing a custom config, but still the default config should be picked up. I have not investigated the issue, I'm assuming it's an issue with the file path in the docker image?

(Sidenote: To me it was not obvious from the readme that the config should be provided inline, making this a bit more clear in the readme would be great, I would gladly provide a PR for that.)

See https://github.com/uhafner/coverage-model

Currently warnings are not shown as annotations in the source files since the corresponding paths are either relative (without preface) or absolute. We should integrate FileNameResolver after reading the reports.

Requirement for #207

We need to use the source code folder as prefix, see Jenkins plugin.

Since we now have a parser registry it makes sense to provide a way to configure the individual tools.

Then we can see if an existing project has been degenerated.

Currently the action is built every time. It would make more sense to publish the whole Docker image to a registry so that we can avoid the build step.

Otherwise it is not clear, which tool is responsible.