-
I couldn't find how to resolve this in the updated github action (failed run). Was there some documented change that I missed? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
I guess setting the projectJDK version is now required, as adding that passes. |
Beta Was this translation helpful? Give feedback.
-
Sorry for re-open this thread, but I'm with the same problem after upgrade from 2022.3 to 2023.1 (Azure DevOps) I've tried to put "projectJDK" (1.8, corretto-1.8, etc.) on my qodana.yaml, but, the same error happen:
It only happen after running with cached data, if I remove task that caches qodana files, my pipeline runs fine. I'm not sure if something else can be done. Something that I've noticed is the message Bellow my qodana.yaml: Good
No Good
Additional, I've rollback my Azure DevOps task from |
Beta Was this translation helpful? Give feedback.
-
I've attached the files. When running with cache (where problem happens), there's no qodana-report-yes-cache.zip I'll prepare execution with this workaround suggested, and come back here latter with results |
Beta Was this translation helpful? Give feedback.
-
@brichbash no good with bootstrap command, see below:
|
Beta Was this translation helpful? Give feedback.
Hello,
Sorry for the inconvenience!
Could you please try setting
projectJDK
once again but also setlinter
. There is a bug that overwritesprojectJDK
if nolinter
is set inqodana.yaml
. Besides, adddownload.jetbrains.com:443
anddownload-cdn.jetbrains.com:443
to the allowed endpoints (the endpoints are used by Qodana to download JDK you set inprojectJDK
. You can see an example of the configuration in the fork (qodana.yaml, qodana.yml)