CodeQl scanning #6116
-
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
We trace those particular Java files that are encountered during a particular build. If you ran |
Beta Was this translation helpful? Give feedback.
-
There could be a number of reasons that the CodeQL analysis only picks up X number of line of code during the build.
In some cases using auto-build or manual build commands there can be some source code that isn't compiled.
Some compilers do not work with CodeQL and can cause issues while analysing the code. RecommendationsFirst is to make sure that you run the exact same build command as you would in production. This makes sure that you are tell CodeQL exactly what to build. Secondly, I recommend downloading the CodeQL database from your Actions workflow. This can be done using the the # ...
- uses: actions/upload-artifact@v2
with:
name: codeql-database
path: ../codeql-database Once you have done that, download the CodeQL Database and find the Hopefully you discover why CodeQL isn't discovering all the source code files or which are the missing and the reason why. |
Beta Was this translation helpful? Give feedback.
There could be a number of reasons that the CodeQL analysis only picks up X number of line of code during the build.
In some cases using auto-build or manual build commands there can be some source code that isn't compiled.
These could be tests, dead code that isn't build or a few other reasons.
Some compilers do not work with CodeQL and can cause issues while analysing the code.
An example of this is Project Lombok where it using non-public compiler APIs in order to achieve the modifications to compiler behavior that it needs.
In doing so, it makes assumptions that are not valid for CodeQL's Java extractor s…