file permissions in artifact is not preserved


the first stage in the build process produces a script that has execution permissions (755). This script is part of the artifact of that stage. The second stage depends on this artifact and expects to be able to run the script. However, the permissions are reset to 644. How do I fix this?



1 answer

1 accepted

0 votes

You have to either recreate the permissions via an Script Task (Inline) or store the artifact in an archive format that preserves permissions (basically, tar the artifact via a Script Task, have the tarrred version defined as an artifact and untar it in the second job - again, via a script task).

Thanks, I will try that.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,066 views 0 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot