Artifact handlers Bamboo administrators can control where artifacts produced by plans are stored. This can help to optimize the utilization of network bandwidth and file system space. You can activate each handler for shared and non-shared artifacts separately. Additionally, you can store artifacts in multiple locations. The default artifact handler selection is configured by a Bamboo admin but can be overridden in a plan's configuration by users that have administration permission on the plan.
To configure artifact handlers, select Administration () > Plans > Artifact handlers.
Types of artifact handlers used by Bamboo
Agent-local artifact handler
This handlers stores the artifact on Bamboo's remote agent's file system. This handler does not publish artifacts to the server (in other words, the artifacts will not be downloadable from result pages if remote or S3 handlers are not enabled). It can be used to save bandwidth when exchanging artifacts between builds & deployments running on the same agent or running on different agents that share a common file system. In the configuration, you need to define the root directory in which all the artifacts will be saved.
Bamboo remote handler
This handler makes artifacts accessible on Bamboo remote and elastic agents. It also allows remote agents to publish artifacts they produce when running builds.
Artifacts are stored in Amazon Simple Storage Service (S3) and are downloadable from there. Amazon S3 offers unlimited flexible storage capacity. For more information about S3, see the Amazon S3 product page.
You can use the AWS credentials provided in the Elastic Bamboo configuration or you can configure a separate account. In either case, you need to provide a bucket name. If you use the same S3 bucket for other purposes, you can provide a root path for all artifacts.
Because the Amazon S3 artifact handler doesn't support IAM role credentials, the Use same AWS credentials as Elastic Bamboo (EC2) option is not available in the Amazon S3 artifact handler if Elastic Bamboo has been configured with an instance profile.
You can also define the maximum number of files per artifact. If the threshold is exceeded, the artifact is automatically compressed into a single
.zip file, reducing the number of requests to S3 when uploading and downloading the artifacts and improving the efficiency of the whole process.
Server-local artifact handler
The server-local artifact handler has been deprecated with Bamboo 8.1. Support for this artifact handler will be removed in a future Bamboo release.