Skip to content

Configure CodeQL to scan Java/Kotlin instead of GitHub Actions (#55) #3

Configure CodeQL to scan Java/Kotlin instead of GitHub Actions (#55)

Configure CodeQL to scan Java/Kotlin instead of GitHub Actions (#55) #3

Triggered via push February 10, 2026 06:37
Status Failure
Total duration 1m 45s
Artifacts

codeql.yml

on: push
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Analyze (java-kotlin)
We were unable to automatically build your code. Please replace the call to the autobuild action with your custom build steps. Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.24.1/x64/codeql/java/tools/autobuild.sh". Exit code was 1 and last log line was: Picked up JAVA_TOOL_OPTIONS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false. See the logs for more details.
Analyze (java-kotlin)
Failed to upload a SARIF file for the unsuccessful execution. Code scanning status information for the repository may be out of date as a result. Processing errors: CodeQL analyses from advanced configurations cannot be processed when the default setup is enabled
Analyze (java-kotlin)
Cannot build an overlay-base database because build-mode is set to "undefined" instead of "none". Falling back to creating a normal full database instead.
Analyze (java-kotlin)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/