Artifact permissions are not preserved for elastic and remote agents using remote artifact handlers

This issue is resolved for elastic and remote agents using remote artifact handlers. Local agents and agents using other handlers (including S3) do not preserve the permissions.

Reproducing issue:

1. create a new Project (i.e.: Support), Plan (i.e.: MyPlan)
2. add an "Script" task

   # creates a new file
   touch executable.jar
   
   # list files
   ls -l
   
   # change its permission
   chmod 755 executable.jar
   
   # list files
   ls -l
   

   As a result you would have something like:

   12-Dec-2014 14:08:52	total 0
   12-Dec-2014 14:08:52	-rw-r--r--  1 root  root  0 Dec 12 14:08 executable.jar
   12-Dec-2014 14:08:52	total 0
   12-Dec-2014 14:08:52	-rwxr-xr-x  1 root  root  0 Dec 12 14:08 executable.jar
   

3. create an Artifact definition as per following:

   Name: myArtifact
   Location:
   Copy pattern: executable.jar
   [x] Shared
   

4. go to "<bamboo-home>/artifacts" and run the following:

   ls -l SUP-MYPLAN/shared/build-00001/myArtifact/executable.jar
   

   As a result you would have something like:

   -rw-r--r--  1 root  root  0 Dec 12 14:08 SUP-MYPLAN/shared/build-00001/myArtifact/executable.jar
   

Workaround

• Write a script job that will re-set the correct permissions
• Tar everything up before creating the artifacts and then pass around a tarball rather than just pure artifacts.