1
votes

I'm using SonarQube 6.2 and I set the Leak Period to "previous_version". However, during analysis, SonarQube detects error in files that were not detected in the previous analysis and in which there was no commit made in the current analysis.

Is this a bug or an issue with my configuration?

1
Could you please share with us the logs that contains the errors ? - Julien L. - SonarSource Team
Thanks for the response. But this is not a system error. They are issues detected in the uncommitted files - philip
What kind of new errors were reported in these files? - Uwe Allner
Critical errors - philip
To clarify: you're seeing new issues raised in code on which there have been no changes? Have you upgraded your analyzer (the language plugin) lately? - G. Ann - SonarSource Team

1 Answers

1
votes

By updating the Java analyzer, new issues are detected on files that were not modified. We're aware of the problem. It's fixed in SonarQube 6.3 with SONAR-8736