Running Bamboo Jobs in a Docker Container Fails with Perforce Clean Build

[Sebastien Erard]

We use Bamboo and Perforce quite happily for 10 years now. We usually configure Bamboo to perform a clean perforce checkout for each build. Our current version of Bamboo is 6.9.2, running on a Centos host, as well as our build agents.

We are trying to get better isolation between tests so we are playing with docker containers to run our build and tests. Unfortunately, it seems Bamboo configure the docker container with a dedicated volume for the run (--volume ${bamboo.working.directory}:${bamboo.working.directory}) where the check out is done, and then delete this directory on the Docker host as part of its clean build procedure with Perforce. This directory is then recreated, the perforce content is properly downloaded. but the docker container still references the old one which is now empty (only the directory lives until the container is destroyed.). The job execution fails as no file is found.

The only workaround is to avoid clean builds, but I would prefer a solution where the clean build is possible.

Is this a known bug? Are there any other suitable workaround?

Thanks for your help.