Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Present summary of Gradle build warnings in Job Summary and PR comment #317

Closed
michael-arndt-gcx opened this issue Jul 31, 2024 · 2 comments

Comments

@michael-arndt-gcx
Copy link

During our build, gradle emits various warnings. Currently they are almost invisible, i.e. we need to look at the log of the workflow run.

Examples for warnings we currently get are:

Gradle deprecation warnings:

The Configuration.fileCollection(Spec) method has been deprecated. This is scheduled to be removed in Gradle 9.0. Use Configuration.getIncoming().artifactView(Action) with a componentFilter instead. Consult the upgrading guide for further information: https://docs.gradle.org/8.9/userguide/upgrading_version_8.html#deprecate_filtered_configuration_file_and_filecollection_methods

kotlin compiler warnings

w: Kapt currently doesn't support language version 2.0+. Falling back to 1.9.

I would like to have some way to collect these and make them visible in a PR. At least as report, preferably as PR comment.

@bigdaz bigdaz changed the title Summary of warnings Summary of warnings as PR comment Jul 31, 2024
@bigdaz bigdaz changed the title Summary of warnings as PR comment Present summary of Gradle build warnings in Job Summary and PR comment Jul 31, 2024
@bigdaz
Copy link
Member

bigdaz commented Jul 31, 2024

Thanks for the idea. Currently we don't have a mechanism to collect these warnings from Gradle, and we don't have any way to parse the GitHub Actions log output either. So I can't see an easy way to do this right now.

However, with the introduction of the Problems API in Gradle we might have a mechanism to collect these warnings.

@bigdaz
Copy link
Member

bigdaz commented Jul 31, 2024

Closing as duplicate of #30

@bigdaz bigdaz closed this as not planned Won't fix, can't repro, duplicate, stale Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants