We're trying to deploy a simple PHP project with no build process, all we need to do in the pipeline is `scp` copy the files up to a remote server.
Here's our pipeline config:
- pipe: atlassian/scp-deploy:0.3.3
SERVER: '<ip addr>'
We want it to put the files from the repo into /var/www/api/v1 on the remote machine, but instead it creates a `build` dir that looks like it has 777 permissions, and puts them in there. (/var/www/api/v1/build/<files>)
Where does this build dir come from? Can we disable that? Or do we have the wrong `LOCAL_PATH` value?
Thank you for your question.
In your case use:
To deploy only files from your directory to the remote you can provide '/local/path/build/*' with trailing asterisk symbol (*) as a LOCAL_PATH variable.
Pipe "SCP deploy" preserves modification times, access times, and modes from the original file. Try to check permissions on your local at first.
But additionally, you can add to your config "SSH run" pipe with a command that modifies targets permissions on the remote:
- pipe: atlassian/ssh-run:0.1.3
COMMAND: 'chmod 755 <your_target_file>'
More information about pipe "SSH run" you can find in the Bitbucket Pipelines SSH run repository.
Atlassian created pipes are kept in the Bitbucket Pipelines pipes project.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
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