Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
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?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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 ...
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!
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