In the New code, the last commit not detected

Ricardo_Emilio_Borto · January 16, 2025, 7:38pm

I use “Enterprise Edition 10.7” and We have the NEW CODE option configured by default (previous version) but in some projects it is not considered new code.
In the latest commits it has not detected new code, do you have any recommendations to do? attached print.

print commit

thanks!!

Colin · January 20, 2025, 1:57pm

Hey there.

This screenshot shows that the last analysis had a warning; what is it?
Does this code show up at all under the Code tab of your project, or is it completely absent (rather than simply not being marked as new code)?

Ricardo_Emilio_Borto · January 23, 2025, 7:48pm

Hey Colin, I answer each questions, at first I attach the print with the warning.

This warning matches with ejecution mode.

Would this affect the operation of the new code?

Next, Respect this question: Does this code show up at all under the Code tab of your project, or is it completely absent (rather than simply not being marked as new code)?
Yes, this code show up at all under the new Code.

Regards!

Colin · January 24, 2025, 10:19am

Yes, if some blame data is missing, that can affect the detection of New Code. It’s very strange that if you’re running your pipeline in a CI/CD context (where all code is committed), you would run into “missing blame information.”

I have a feeling that the screenshot of the logs you’re sharing probably don’t come from the analysis when this new code was first analyzed.

Let’s try this another way – do you see blame data for the file in SonarQube?

By this I mean returning to the file under the Code tab in SonarQube and clicking on the space between the line number and the code, specifically for a line of code shared in the Bitbucket screenshot.