Trigger analysis on file save

  • Operating system: Linux (Debian testing)
  • SonarLint plugin version:
  • Programming language you’re coding in: Java
  • Is connected mode used: Yes
    • Connected to SonarCloud or SonarQube (and which version): SonarQube, unknown version

And a thorough description of the problem / question:

Currently there only seems to be two modes of triggering analysis. WIth “Automatically trigger analysis” enabled it will trigger as soon as I start modifying a file. This makes the IDE slow. With “Automatically trigger analysis” disabled it will never trigger automatically.

Is it possible to make it trigger analysis whenever a file is saved?

Hello Simon,

Before introducing a new feature, I would like to understand why the analysis is slow on your side. First what do you mean by slow ? Do you have big files and how many lines are they ?

It could be related to some slow rules when analyzing the code, and I want to understand if it’s the case. Would you be able to send us a reproducer of what you consider to be a slow file ?

1 Like