New code analysis is not happening correctly on sonar community 8.6 version

Must-share information (formatted with Markdown):

  • which versions are you using :SonarQubue commutniy edition 8.6
  • what are you trying to achieve: Sonar has to analysis source code based on ‘New code’ concept.
  • what have you tried so far to achieve this: Defined analysis to consider ‘Newcode’ based on ‘previous commit’ instead of ‘Overall code’. and we are pushing code to gerrit so that jenins job will trigger automatically. We configured in such a way that every push can be consider as ‘New code’ so that one developer code push is independent of other developer code push.
    Sometimes analysis happening correctly and issues are displaying on New code and same issues are assigned to developer name who has pushed the code (we are using JIRA).But some times it’ s not happening. That means analysis is happening on the other files/legacy code which are not modified by current build developer and also issues details are assigning to some other developer. If you push the same code again happening correctly. Not sure what is the mistake here.
    Could you please let me know why this is happening. How to overcome this issue.


2 posts were merged into an existing topic: Sometimes sonarqube doing analysis on legacy code even though we have defined as to consider ‘New Code’