We have Atlassian Bamboo running on Ubuntu. When a developer is setting up a build, then he has the possibility to run shell script tasks. This is useful to run (custom) commands on the codebase you are building.

However, the scripts that run can also access the filesystem outside their job directory in the Bamboo working directory (<Bamboo-home-dir>/xml-data/build-dir/JOB_KEY). So JOB_A can also access files of JOB_B: cd ../JOB_B.

Is there a possibility to restrict this access?

P.S. I am aware of the fact that builds are ran by (local or remote) agents in Bamboo and you can build different projects by different agents. However, if two projects are built by the same agent, the projects could access each other's files.

We have Atlassian Bamboo running on Ubuntu. When a developer is setting up a build, then he or she has the possibility to run shell script tasks. This is useful to run (custom) commands on the codebase you are building.

However, the scripts that run can also access the filesystem outside their job directory in the Bamboo working directory (<Bamboo-home-dir>/xml-data/build-dir/JOB_KEY). So JOB_A can also access files of JOB_B: cd ../JOB_B.

Is there a possibility to restrict this access?

P.S. I am aware of the fact that builds are ran by (local or remote) agents in Bamboo and you can build different projects by different agents. However, if two projects are built by the same agent, the projects could access each other's files.