Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

BITBUCKET_PIPE_STORAGE_DIR is read-only on subsequent pipe invocations

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.

2 answers

0 votes

@Tom McLaughlin  Thank you with full clarification. 

0 votes

@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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

1,001 views 20 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you