Micro Focus Contributor
Micro Focus Contributor

<QC/ALM Support Tip> Project Repository Cleanup



In the post below, you may find useful information, how to perform a cleanup of the Project Repository and which parameters should be used:


When you add a file to an entity, ALM checks whether an identical file exists in the project repository. If an identical file is located, no physical file is added to the repository.

When you delete a file from an entity, the file is not immediately deleted from the project directory, as it may still be used by other entities.

At regular intervals, the project repository is scanned for obsolete files that are no longer referenced by any entity.

If the files remain unreferenced for a specified period, they are removed from the project repository. These intervals are set by default at seven days each.

You can configure the intervals using the site configuration parameters below.

You can promote or postpone a project's repository cleanup. 

You can define the following site configuration parameters to regulate the project repository cleanup



REPOSITORY_GC_PROJECT_CLEANUP_INTERVAL. Defines the time interval between cleanup processes of each project repository.

This parameter defines the time interval in days between cleaning processes of each project repository.

Set a value in days between and 28. If the parameter does not exist, ALM scans project repositories once every seven days.


REPOSITORY_GC_DELAY_CANDIDATE_TIME. Defines the time that elapses after obsolete files are detected in a scan, and before the obsolete files are removed.

This parameter enables you to create a delay between the time of the cleaning processes of each project repository and the time the files without references are actually deleted.

Set a value in days between and 28. If the parameter does not exist, ALM delays the deletion of obsolete files in the file system for even days.



REPOSITORY_GC_JOB_PRIORITY. Defines the speed at which the cleanup process is performed. The parameter determines the speed at which the repository cleanup process is performed.

Set a value  between (fastest) and 10 (slowest). If the parameter does not exist, the speed is set to 3.


SUSPEND_REPOSITORY_GC. Enables you to stop the project repository cleanup process.

This parameter relates to the project repository cleaning process. The parameter stops the cleanup process on the entire site.

Use this only in special circumstances. For example, to check if the cleanup process is impacting system performance.

Define this parameter and set its value to to temporarily stop the project repository cleaning process. To restart the cleaning process, set the parameter to N.



I hope that you will find the information provided, useful.


Best Regards,


HP QC/ALM Support

"HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution."
Labels (1)
Tags (3)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.