ArtifactsCachePublisher VS WebPublisher

Hi,

sorry for the delay. The publishers do what you meant, the WebPublisher, more than "available to download via TeamCity web interface", posts them back to the TeamCity server, where they are used for internal purposes, as some internal, hidden artifacts are published for every build including properties, logs, etc.

Disabling the ArtifactsCache is possible and specified in our documentation here: https://confluence.jetbrains.com/display/TCD10/Free+disk+space#Freediskspace-Configuringartifactscache

Before deactivating them, though, we would like to ask why you want to disable them.

Hi Denis,

Thanks for your response, one of our artifacts is taking more than 3 hours to create (around 3.5 GB) , as such we do not have a need to publish this artifact but there is a requirement to make this artifact available via TC UI.

HTH

Hi,

if you need to have the artifact displayed in the UI, teamcity needs to have it in the server. Artifacts are generated in agents, so it needs to be "published" (a.k.a. transferred) to the server, so I'm afraid that the WebPublisher will need to stay if you need the artifact to be displayed in the UI.

If you don't need the file to be available in the server (if you use the UI only to confirm it was created, not for download, nor used as artifact dependency for any subsequent build, just used in a following build step to deploy, for example), you might consider adding a new build step with a verification that the file was correctly created, create an empty file confirming its creation and then simply publishing that as the artifact, so users can have the reference that the file was created.

Even though we have disabled the artifact cache still teamcity is trying to update the artifact.

We have set this property in agent configuration property

Hi. This output is normal. You should see this line in the verbose build log:

Publishing to local artifacts cache is disabled, skipping.