# New lines for specific analysis as baseline

**URL:** <https://community.sonarsource.com/t/new-lines-for-specific-analysis-as-baseline/147679>\
**Category:** SonarQube Server / Community Build\
**Created:** [August 29, 2025, 11:27am UTC](https://community.sonarsource.com/t/new-lines-for-specific-analysis-as-baseline/147679 "2025-08-29T11:27:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peteris](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@Peteris](https://community.sonarsource.com/u/Peteris)\
**Post date:** [August 29, 2025, 11:27am UTC](https://community.sonarsource.com/t/new-lines-for-specific-analysis-as-baseline/147679/1 "2025-08-29T11:27:41Z")

</div>

- which version - v24.12.0.100206
- how deployed: Docker
- what are you trying to achieve - get correct new lines for sonarqube project that have “specific analysis“ as baseline
- what have you tried so far to achieve this - upgraded sonarqube, set baseline, run analysis

Hi.  
I am getting problems with new lines - we run sonar analysis, set up first analysis as baseline, then there was few analysis with minimal amount of new code and everything looked fine.  
But then into branch (from which analysis was done) was merged another branch that introduced big amount of new code - aaaand it was not fine any more because it is clear that that many lines of new code does not show as new lines.

As I understand “specific analysis“ as baseline for new code should be exactly that - baseline and all code from new sonar analyses that is not in that baseline analysis should be new code. But currently it does not work that way.  
Why?  
Not sure what provide here for investigation…

So far I tried to investigate and although I did not looked through all code (at least yet) but noticed so far that code commits that did not show as new code is older than commit from which first analysis-baseline was done.

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [September 1, 2025, 10:13am UTC](https://community.sonarsource.com/t/new-lines-for-specific-analysis-as-baseline/147679/2 "2025-09-01T10:13:13Z")

</div>

Hey there,

> [@Peteris](#):
>
> which version - v24.12.0.100206

Only the latest version of SonarQube Community Build is considered active, so you’ll need to update and see if the situation is still replicable before we can help you.

> 24.12 → 25.8

You may find these resources helpful:

- [Update Guide](https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/upgrade/upgrade-the-server/roadmap/)
- [SonarQube Community Build Update Notes](https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/release-notes-and-notices/release-upgrade-notes/) (all update notes since the switch)

If you have questions about upgrading, feel free to open a new thread for that [here](https://community.sonarsource.com/c/sq/10).

If your issue persists after updating, please come back to us.