Sonarqube Community edition v9.9.4 - Baseline analysis commit for new code disappear after 10 days

We are using SonarQube Community Edition v9.9.4, deployed using a zip file. In the project settings, we selected a specific analysis as the baseline for new code analysis. Initially, this worked as expected: for 7-10 days after the settings update, new code commits were analyzed against the baseline commit. However, the baseline commit then disappeared from the analysis list, even when selecting “All time” from the dropdown. Consequently, subsequent commits treat all code as new, leading to full code scans instead of incremental scans, which ultimately fail.

As a workaround, we are updating the baseline commit every 10 days to make it work.

However, we are seeking a more permanent solution. Are there any plugins available that would allow us to retain the baseline commit for longer than 10 days? or any other solution to fix this issue ?

Hey there!

I thought that maybe there could be a bug where we don’t check a specific analysis was used as the baseline before purging old analyses (housekeeping) but I couldn’t reproduce that. :confused:

Do you still see the analysis in the Activity section of your project?

Hi Colin, Sorry for the late response. Yes I can see them in the activity section.

Hey @MohamedRabiyudeen

If you’re still facing the issue, do you mind sharing a screenshot where you have the analyses available to view in the Activity section but you cannot select them as a baseline?