Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Changing Artifact path to network attach storage

I've setup and configured bamboo instance on Azure VM and it was okay for few month until we reach the storage limit due to size of artifacts generated from each build. 

So we decided to attach Azure storage(NAS) to the bamboo server(VM) so that we can store the artifacts on the Azure storage

I configured the bamboo artifact directory by following instruction on this page:

So basically I create artifacts folder in Azure storage so that the path to the artifact directory is something like /nasshare/bamboo/artifacts where /nasshare is Azure storage mounted on Bamboo server. 

However, when bamboo runs a build plan which generates and greeting.txt as a artifact, I get following errors: /opt/bamboo/bamboo-home/artifacts2/plan-11468801/JOB1/build-00006/greeting/greeting.txt: Operation not permitted

Unable to publish artifact [greeting]: Unable to publish artifact Job artifact: [greeting], pattern: [greeting.txt] for BAMT-AT-JOB1-6 via

When I check the directory, Bamboo actually creates greeting.txt file on that path but for some reason i fails to publish it and generate such error.

I have checked ownership and permissions for nasshare/bamboo/artifacts, the owner:group is not the same user and different group from the bamboo user but permission is actually 777. so should not be permission issue i guess..

Any idea how to resolve this?


Thank you

1 answer

0 votes

Hi Brent,

If I am correct using Bamboo 6.2 or higher which has Artifact Handler Feature. This feature has different options available to configure upon which creation and publish of artifacts depends.

Creation and publish of artifacts in Bamboo are two different things.
If Bamboo is able to create the artifacts but unable to publish them then I think you are missing some configuration here and resulting in the above error.

You can refer this document to see what configuration will suit your requirement:



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

191 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you