This version of the SonarQube documentation is no longer maintained. It relates to a version of SonarQube that is not active.

See latest version
Start Free
10.1 | Project administration | Managing project history

Managing project history

On this page

One of the most powerful features of SonarQube is that it shows you not just your project health today, but how it has changed over time. It does that by selectively keeping data from previous analyses (see Housekeeping). It doesn't keep all previous analyses. That would bloat the database. Similarly, for the analyses it does keep, SonarQube doesn't keep all the data. Once a project snapshot moves from being the "last analysis" (i.e., the most recent) to being part of the project's history, data below the project level is purged to keep from bloating the database.

Typically these aren't things you need to even think about. SonarQube just handles them for you. But occasionally you may need to remove a bad snapshot from a project's history or change the housekeeping algorithms.

Managing history

Occasionally, you may need to manually delete a project snapshot, whether because the wrong quality profile was used, or because there was a problem with analysis, and so on. Note that the most recent snapshot (labeled Last snapshot) can never be deleted.

At the project level, from the front page Activity list, choose Show More to see the full activity list.

For every snapshot, it is possible to manually:

  • Add, rename or remove a version.
  • Add, rename or remove an event.
  • Delete the snapshot.

Was this page helpful?

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARLINT, SONARQUBE, SONARCLOUD, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Creative Commons License