Buttons for Managing an Existing Repository in Nexus Repository

The Invalidate cache button on a proxy or group repository's administration screen expires the previously cached maximum metadata age and maximum component age values for components. The next request for a component will cause a proxy repository to query the remote repository to obtain metadata for available versions of the component. Components previously downloaded to the proxy repository are not deleted from storage, so they will not be retrieved again from the remote if they have not changed. Invalidating cache also purges the contents of the not found cache.

Invalidating the cache for a group repository clears the group cache so that any items fetched and held in the group cache, such as Maven metadata, are cleared. Invalidating a group cache also impacts all proxy and other group repositories that are members of the group. Since invalidating cache results in extra queries to the remote repository, targeting specific repositories is better for performance.

Invalidating the cache does not delete components previously downloaded to the proxy repository from storage. They will not be retrieved again from the remote if they have not changed.

The Rebuild Index button allows you to remove and recreate an individual proxy or hosted repository's search index to synchronize repository contents with the search index. This button is available for proxy and hosted repositories. Note that the button is specific to the search index and does not rebuild the index.yaml file.

Note that the Rebuild Index button works on a single repository. If you need to rebuild the search index for all repositories, use the Repair - Rebuild repository search task.