Details
-
Suggestion
-
Resolution: Fixed
Description
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:
- create a new Project (i.e.: Support), Plan (i.e.: MyPlan)
- 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
- create an Artifact definition as per following:
Name: myArtifact Location: Copy pattern: executable.jar [x] Shared
- 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.
Attachments
Issue Links
- is duplicated by
-
BAM-15581 Preserve file permissions in artifacts
- Closed
- relates to
-
BAM-17770 Artifact permissions are not preserved for local agents
- Closed
-
BAM-17806 Shared artifact built on remote agent does not preserve permissions with a Windows Bamboo Server
- Gathering Interest
- was cloned as
-
BDEV-7141 Loading...