Bamboo Remote Agent Share Artifacts across Plan and Deployment Multiple Agents

[Brightson Macha]

I have five remote agents. A Plan-Build to build an application and publish current directory as artifact Plan-Artifact (location: . , copy-pattern: */, shared, comprased). This Plan-Artifact is then used in my deployment stage. If the same agent publish artifact is used for deployment, no problem. But if different agent used other than the publisher of artifact, then getting below error. How to resolve, any way around that.?

ERROR

---

27-Aug-2025 15:58:36 Build Deployment of 'NFTP-23' on 'PREPROD' is being prepared for building on agent bambooAgent2 (2), bamboo version: 9.5.1

27-Aug-2025 15:58:36 Remote agent on host bambooAgent2

27-Aug-2025 15:58:36 Build working directory is /var/atlassian/application-data/bamboo-agent/xml-data/build-dir/92831745-92536837

27-Aug-2025 15:58:36 Executing build Deployment of 'NFTP-23' on 'PREPROD'

27-Aug-2025 15:58:36 Starting task 'Download release contents' of type 'com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:artifactdownloadertask'

27-Aug-2025 15:58:36 Preparing to download plan result APP-NFT-23 artifact: Required shared artifact Http Compression On : [Company Fund Transfer PAPI Artifact], patterns: [*/] anchored at: [.]

27-Aug-2025 15:58:36 /var/atlassian/application-data/bamboo-agent/bin/plan-88211520/shared/build-00023/Company-Fund-Transfer-PAPI-Artifact is not a directory

27-Aug-2025 15:58:36 Unable to download artifact Required shared artifact Http Compression On : [Company Fund Transfer PAPI Artifact], patterns: [*/] anchored at: [.]

27-Aug-2025 15:58:36 This deployment task inherits artifact handler configuration from the source plan.

27-Aug-2025 15:58:36 The plan is using custom artifact handlers configuration.

27-Aug-2025 15:58:36 The following handlers are enabled for transferring shared artifacts:

27-Aug-2025 15:58:36 custom.artifactHandlers.comAtlassianBambooPluginArtifactHandlerRemote:BambooRemoteArtifactHandler

27-Aug-2025 15:58:36 custom.artifactHandlers.comAtlassianBambooPluginArtifactHandlerRemote:AgentLocalArtifactHandler

27-Aug-2025 15:58:36 Task configuration:

27-Aug-2025 15:58:36 artifactName_0 -> [ready-for-deploy]

27-Aug-2025 15:58:36 artifactId_0 -> [88735747]

27-Aug-2025 15:58:36 sourcePlanKey -> [APP-NFT]

27-Aug-2025 15:58:36 localPath_0 -> []

27-Aug-2025 15:58:36 Task runtime configuration:

27-Aug-2025 15:58:36 securityToken -> [a6d603dc822d2458065565d332887b9c3553a750]

27-Aug-2025 15:58:36 resultKey -> [APP-NFT-23]

27-Aug-2025 15:58:36 sourcePlanOrBranchKey -> [APP-NFT]

27-Aug-2025 15:58:36 Finished task 'Download release contents' with result: Error

27-Aug-2025 15:58:36 Starting task 'Clean working directory task' of type 'com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:cleanWorkingDirectoryTask'

27-Aug-2025 15:58:36 Cleaning working directory '/var/atlassian/application-data/bamboo-agent/xml-data/build-dir/92831745-92536837'

27-Aug-2025 15:58:36 Finished task 'Clean working directory task' with result: Success

---

[Shashank Kumar · Accepted solution]

Hello Brightson,

Welcome to Atlassian community.

There seems to be 2 artifact handler configured on your plans

BambooRemoteArtifactHandler and AgentLocalArtifactHandler

Can you remove AgentLocalArtifactHandler and re run the plan and then the deployment and see if it works.

Regards,

Shashank Kumar

**please don't forget to Accept the answer if your query was answered**

[Brightson Macha]

Please see below screenshot and suggest if that the way to go.

Initial:

When Tick artifact handler:

[Shashank Kumar]

Hello Brightson,

Yes that's the right way to do it, do give it a try and run a new build and a new deployment and see if it helps.

Regards,

Shashank Kumar

[Brightson Macha]

Great, thanks