BITBUCKET_PIPE_STORAGE_DIR is read-only on subsequent pipe invocations

[Tom McLaughlin]

We can only write files to BITBUCKET_PIPE_STORAGE_DIR the first time our pipe runs for a particular build.

We have a pipe which runs in different steps as part of the same build. The first time we run it, we see BITBUCKET_PIPE_STORAGE_DIR Mounted this way:

drwxr-xr-x. 2 root root 4.0K Apr 29 17:08 /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/avantas/ecs-pod-deploy

The next time, it is mounted this way:

drwxr-xr-x. 2 65534 65534 4.0K Apr 29 17:08 /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/avantas/ecs-pod-deploy

In the subsequent pipe executions, we cannot write to or delete files from $BITBUCKET_PIPE_STORAGE_DIR.

As an example, if I make a pipe that does this:

 touch "$BITBUCKET_PIPE_STORAGE_DIR/$BITBUCKET_BUILD_NUMBER.tmp"

If we run the same pipe on two subsequent build steps, we will encounter this:

touch: cannot touch '/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/avantas/ecs-pod-deploy/847.tmp': Permission denied

I believe this is a regression.

[Halyna Berezovska]

@Gonchik Tsymzhitov @Tom McLaughlin thanks for reporting it. This is a bug and right now in our priority to fix.

Temporary workaround is put such lines before second execution of pipe :

- BITBUCKET_PIPE_STORAGE_DIR=.... <the issued directory>

- chmod +rw $BITBUCKET_PIPE_STORAGE_DIR

Regards, Galyna

[Gonchik Tsymzhitov]

@Tom McLaughlin  Thank you with full clarification.