-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
--build-mode=none runs the autobuild script for Java on CentOS 7 #16202
Comments
Hi @abaveja313 👋 The |
Ok, got it, thanks! |
@mbg Do you have any suggestions as to how to make the database creation process faster? |
Going by the log you posted, it looks like the database creation is already pretty quick. What are you hoping for? |
Specifically the Maven activity you can see here is the result of querying dependencies, not actually building the project, hence Maven's completion in 10 seconds including fetching jar files. |
I am encountering an issue with CodeQL version 2.17 when using the new
--build-mode=none
option for Java on CentOS Linux 7 (Core). Despite specifying this option in thecodeql database create
command, the autobuild script is still executed, resulting in the project being built. Are there any workarounds to make this work?Steps to Reproduce
codeql database create
command with the--build-mode=none
option:Expected Behavior
When specifying the
--build-mode=none
option, I expect the autobuild script not to be executed and the project not to be built. I am trying to optimize the speed of the database creation.Actual Behavior
Despite using the
--build-mode=none
option, the autobuild script is still executed, and the project is being built. This can be observed in the logs, where the Maven build process is initiated and dependencies are downloaded.Environment
Additional Information
I would appreciate any assistance in resolving this issue and ensuring that the
--build-mode=none
option works as expected, preventing the autobuild script from running and building the project.Thank you for your help!
The text was updated successfully, but these errors were encountered: