You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
bigdaz
changed the title
Summary of warnings
Summary of warnings as PR comment
Jul 31, 2024
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
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.
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:
kotlin compiler warnings
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.
The text was updated successfully, but these errors were encountered: