We’re using scanner property sonar.eslint.reportPaths to feed generated es lint reports to sonar 10.0. This works well however for new analysis we seem to see new issues reported when the code files weren’t changed in source control. The issues are pre existing from the earlier analysis and still appear in the “new code” issues tab
It sounds like you’re expecting newly-reported 3rd-party issues to be backdated. Unfortunately, that’s just not how it works. There are only certain circumstances where backdating kicks in.
thanks @ganncamp no actually this isn’t related to back dating. I wouldn’t mind seeing any profile changes for old code mentioned in the “new code” metrics. However what happens if we then make a small change to one file to add a new issue or two in the next analysis we see far more issues occur in the “new code” metric still. Is there any part of the logs we could review to help more if this isn’t expected behaviour?
There’s not particular logging related to this. Could you share a screenshot of the problem? I’m not able to visualize it.
thanks @ganncamp , can I privately send to you? Then we can follow up with the outcome
Could you just redact as necessary?