CodeQL Failed - Exit code was 32 and error was: CodeQL detected code written in Java/Kotlin but could not process any of it.

[hanwenzhang123]

Select Topic Area

Question

Body

I set up .github/workflows/codeql.yml as of

    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v2
      with:
        category: "/language:${{matrix.language}}"
        upload-database: false

Got an error when running Perform CodeQL Analysis
Exit code was 32 and error was: CodeQL detected code written in Java/Kotlin but could not process any of it.

Any advice on how to fix it? Thank you

[aibaars]

Have you read the troubleshooting guide mentioned in the error message? https://docs.github.com/en/code-security/code-scanning/troubleshooting-code-scanning/no-source-code-seen-during-build

Could you provide a bit more context? Before github/codeql-action/analyze step, does your workflow file contain a github/codeql-action/init step followed by either a github/codeql-action/autobuild step or an explicit build command? If you have all that, then most likely the "autobuild" or explict build command did not compile and Java or Kotlin code.

[hanwenzhang123]

Hi @aibaars,
The autobuild failed. So I am building the project manually.
Here is more context of the script before the analyze

    - name: Build Java project
      run: mvn -B package --file code/SoloSavingsApp/pom.xml

    - name: Initialize CodeQL
      uses: github/codeql-action/init@v2
      with:
        languages: ${{ matrix.language }}

    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v2

[aibaars]

I see, you need to put the explicit build command between the github/codeql-action/init and the github/codeql-action/analyze steps. The github/codeql-action/init step switches on the CodeQL "build tracer" which inspects the compiler processes while the build is running. For things to work the "build tracer" needs to be switched on before running the build command.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬