How to prevent Pipelines from fuzzing with the file permissions

Hello, we are currently starting to use Pipelines as our main CI/CD-Tool for customer websites.

We maintain correct directory and file permissions by using the right ones locally and commit them to the repository. This way every system that users the code from the repository is guaranteed to have the right permissions set.

Now Pipelines, as one of it's first actions, chmods the whole directory to 777 and I can not find a way to disable this behaviour.

We don't want to sync the files/directories with 777 to the webserver, because we don't want to allow the webserver itself to write to all its directories...

We also use our own Docker image for the builds.

Is there a way to work around this?

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,942 views 1 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you