Bamboo Artifact Handlers - Use Case Scenarios

Still need help?

The Atlassian Community is here for you.

Ask the community

Purpose

In Bamboo 6.2 a new feature called "Artifact Handlers" was introduced which lets you control where artifacts produced by plans are stored as described here. But, the user might face difficulties in understanding the use case of the options available under this feature to manage your artifacts. This guide will help you understand the possible use case scenarios to understand these options further.

Solution

The below matrices will cover possible combinations of the available options in different use case scenarios.
The following legend will be used to simplify the data representation.

Legend Comment
- The artifact can't be either published or downloaded
The artifact can be created and published
The artifact can be downloaded
The artifact can't be downloaded


Case 1:

  • PLAN A is used for creating and publishing artifact using a local agent 1
  • PLAN B is used for downloading the artifact using local agent 2.
Local Agent 1(PLAN A for creating and publishing artifacts) Local Agent 2(PLAN B for downloading artifacts)
Agent-local artifact handler Bamboo remote handler Amazon S3 Server-local artifact handler
Agent-local artifact handler - - - -
Bamboo remote handler - - - -
Amazon S3




Server-local artifact handler




Case 2:

  • PLAN A is used for creating and publishing artifact using a local agent 1
  • PLAN B is used for downloading the artifact using remote agent 1
Local Agent 1(PLAN A for creating and publishing artifacts) Remote Agent 1(PLAN B for downloading artifacts)
Agent-local artifact handler Bamboo remote handler Amazon S3 Server-local artifact handler
Agent-local artifact handler

- - -
Bamboo remote handler - - - -
Amazon S3




Server-local artifact handler





Case 3:

  • PLAN A is used for creating and publishing artifact using a remote agent 1

  • PLAN B is used for downloading the artifact using local agent 1

Remote Agent 1(PLAN A for creating and publishing artifacts) Local Agent 1(PLAN B for downloading artifacts)
Agent-local artifact handler Bamboo remote handler Amazon S3 Server-local artifact handler
Agent-local artifact handler







Bamboo remote handler





Amazon S3




Server-local artifact handler - - - -

Case 4:

  • PLAN A is used for creating and publishing artifact using a remote agent 1

  • PLAN B is used for downloading the artifact using remote agent 2

Remote Agent 1(PLAN A for creating and publishing artifacts) Remote Agent 2(PLAN B for downloading artifacts)
Agent-local artifact handler Bamboo remote handler Amazon S3 Server-local artifact handler
Agent-local artifact handler







Bamboo remote handler




Amazon S3




Server-local artifact handler - - - -
Last modified on Jul 13, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.