Message-ID: <106830824.3311.1425139983550.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3310_493466334.1425139983549" ------=_Part_3310_493466334.1425139983549 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
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 t= hat by selectively keeping data from previous analyses. It doesn't keep all= previous analyses - that would bloat the database. Similarly, for the anal= yses it does keep, SonarQube doesn't keep all the data. Once a project snap= shot moves from the the "Last analysis" (i.e. the most recent) to= being part of the project's history, data below the project level is purge= d - again to keep from bloating the database.
Typically these aren't things you need to even think about; SonarQube ju= st handles them for you. But occasionally you may need to remove a bad snap= shot from a project's history or change the housekeeping algorithms. <= /p>
Every snapshot with an event is ignored by the housekeeping algorithms, = and retained indefinitely in the database. There are four types of events:<= /p>
As previously mentioned, when you run a new analysis of your project, so= me data that was previously available is cleaned out of the database. For e= xample the source code of the previous analysis, measures at directory and = file levels, and so on are automatically be removed at the end of a new ana= lysis. Additional, some old analysis snapshots are also removed.
It is useful to analyze a project frequently to see how its quality evol= ves. It is also useful to be able to see the trends over weeks, months, yea= rs. But when you look back in time, you don't really need the same level of= detail as you do for the project's current state. To save space and to imp= rove overall performance, the Database Cleaner deletes some rows in the dat= abase. Here is its default configuration:
These settings can be changed at Settings > General Sett= ings > General > Database Cleaner.
Occasionally, you may need to manually delete a project snapshot, whethe= r because the wrong quality profile was used, or because there was a proble= m with analysis, and so on. Note that the most recent snapshot (labeled &qu= ot;Last snapshot") can never be deleted.=20 =20
At project level, go to Configuration > History= .
For every snapshot, it is possible to manually: