Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Failure in artifact preparation phase during processing of: Subscription for Non required shared art

Failure in artifact preparation phase during processing of: Subscription for Non required shared artifact: [src], pattern: [**/*.*] anchored at: [src], destination: [src]


2 answers

Hello Sadhana

I know its late response :-) - posting here so someone with similar error might benefit 

In my Bamboo agent log I see following error 

2021-01-15 13:42:07,532 ERROR [2-BAM::sles12sp3-agent4::Agent:pool-5-thread-1] [BambooArtifactHttpTransport]
org.apache.http.TruncatedChunkException: Truncated chunk (expected size: 8,192; actual size: 4,202)

Do you see similar messages in your Bamboo agent log ? 

If this is the case then it means there is an issue with Bamboo server to agent communication that is affecting transfer of artifacts 

In that case you might want to use the workaround that I employed only if your default local agent can run the task that is dependent on shared artifacts being copied.

I changed requirements of the task dependent on artifacts  to run locally on Bamboo default agent 

Alternatively you might want to fix the cause for that exception by adjusting time outs  - see -


By the way, did you see Dan turner's question - That solution does not work for me though and I had to use above workaround 

Best regards 


Any reply Please

please see  response below 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events