Hi Luke,
Long time no talk. I hope all is well and your holidays are happy. Regarding this request for information, can you have a look at the doc here: How to purge Release Automation artifacts via Sonatype Nexus?
I'm 99.9999% certain that CA Release Automation will not periodically delete any of your artifacts. And there is no policy that I'm aware of. The doc walks through removing the artifacts through the Nexus UI which I believe would be considered best practice since:
a. Deleting the artifacts in RA UI doesn't remove the artifacts from nexus.
b. Deleting the files from disk would leave orphaned indexes in Nexus. If this happens I'm not sure how Nexus handles this (performance or cleanup wise).
The only issue with removing the files from Nexus is that jobs might fail if:
a. the original source of the artifacts are not available;
b. the artifact is not in nexus anymore.
Some time ago (probably before storing artifacts in local repo option was made available) a best practice was shared with me by a product manager that using an external artifact repository was preferred over use of the local nexus repo used by the management server since:
a. using an external repo would be sure to not use resources (cpu, mem, disk io, network, etc..) on the management server during jobs in an active environment.
b. the internal nexus repository is not an enterprise install of an artifact repository. it was installed and used, from the beginning, to meet the needs of the management server and the management of the library files used by it and throughout the environment (like actionpacks, etc..) specific to the product.
I'm not trying to completely steer you away from changing how you use Nexus. I'm just sharing everything I know on the matter. Do let us know if you have any other problems and/or questions.
Cheers,
Gregg