You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're experiencing heavily different results on the same codebase when executing Qodana IntelliJ plugin compared to the docker containers that are being used in CI pipelines.
(we're storing codestyle and inspection configuration of IntelliJ in the git repository that's being analyzed)
Today we figured out that the plugin respects special rules for Spring Boot annotations where the container "qodana-jvm-community" raises inspection errors like "variable is not set anywhere" (on @Autowired injected variables).
Hence we suspect that the plugin does not respect the linter configuration option in qodana.yaml file.
There are many other differnences between both analyzes.
We aim to have identical results locally (plugin) and in the pipeline (container).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're experiencing heavily different results on the same codebase when executing Qodana IntelliJ plugin compared to the docker containers that are being used in CI pipelines.
(we're storing codestyle and inspection configuration of IntelliJ in the git repository that's being analyzed)
Today we figured out that the plugin respects special rules for Spring Boot annotations where the container "qodana-jvm-community" raises inspection errors like "variable is not set anywhere" (on @Autowired injected variables).
Hence we suspect that the plugin does not respect the linter configuration option in qodana.yaml file.
There are many other differnences between both analyzes.
We aim to have identical results locally (plugin) and in the pipeline (container).
Any idea?
Beta Was this translation helpful? Give feedback.
All reactions