When RA distirbutes the artifacts to agents, does RA retain the artifacts in target servers even after the deployment is completed ? If yes, what is the retention policy and is it configurable ?
Thanks & Regards
Artifacts are stored in the following location during deployment.
Execution Server : <ReleaseAutomationInstallDir>\artifact-store\<releaseId_xx>Agent : <ReleaseAutomationInstallDir>\NolioAgent\artifact-store\<releaseId_xx>
Artifacts are always removed from the artifact-store once deployment is complete as outlined by others.
If you are still seeing artifacts in the store post deployment, I recommend you to open a support case for further investigation.
When an artifact gets distributed, the file is placed temporarily on the machine (within the nolioAgent/artifact_store/releaseId_.../ directory structure). To get the file to persist after the deployment you need to use something like the copy file action to put the file where you want it. You do this by creating a flow that is configured to loop on the "Collection Element" associated with that artifact. Once that is done you can add a copy file action and use the artifacts parameter: Artifact File as a source parameter.That parameter will give you a reference of the file in its temporary location on the agent machine to allow you to copy it to a more permanent place.
But my question was about the artifacts getting retained in the artifact_store path. I am in understanding that after the deployment is complete, the artifacts will get deleted automatically. However, are there any cases for the artifacts to not get deleted from the artifact_store path ? If yes, what are those cases and for how many occurences will it retain.
in all of my deploys, the artifacts were deleted automatically
Correct. Unless something extraordinary happens, like the agent crashing, the artifacts will be removed from their temporary storage at the end of the deployment.
we noticed that the artifacts from past 5 deployments were still present in the artifact_store even after the deployment was completed successfully.
On which RA release are you , there where some fixes around this in the latest versions and builds
We are on 220.127.116.1122.
Retrieving data ...