TeamCity stores artifactsproduced by builds on the file system accessible by the TeamCity server. The default location is <Teamcity Data Directory>/system/ artifacts but this location can be redefined.
External Artifacts Storage
Starting from version 2017.1, TeamCity provides a pluggable API to enable external storage for TeamCity build artifacts. Support for different storages can be implemented as an external plugin to TeamCity: the details are provided in the external storage implementation guide.
tip
Note that when an external storage for artifacts is enabled, the TeamCity internal artifacts (including build logs) will still be published to the TeamCity server.
The same applies to the metadata about artifacts mappings, which will be published to the artifacts directory of the TeamCity Data directory. When restoring from a backup, make sure they are restored for the external artifact plugin to work properly.
Several experimental non-bundled plugins developed by JetBrains are listed below.
Amazon S3 Support
Amazon S3 Artifact Storage is supported via an experimental external plugin from JetBrains, teamcity-s3-storage-plugin. When installed and configured, the plugin allows uploading to, downloading and removing artifacts from S3; it handles resolution of artifact dependencies as well as clean-up of artifacts. The plugin also displays artifacts located externally in the TeamCity web UI.
Azure Artifact Storage
Azure Artifact Storage is an experimental plugin by JetBrains which allows replacing the TeamCity built-in artifacts storage by Azure Blob storage.
Google Cloud Artifact Storage
Google Cloud Artifact Storage is implemented as a plugin by JetBrains.