Pipelines "scp-deploy" puts everything in "build" dir on the remote server

Duncan MacKenzie

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:

image: php:5.6.30

pipelines:
branches:
master:
- step:
script:
- pipe: atlassian/scp-deploy:0.3.3
variables:
USER: '<username>'
SERVER: '<ip addr>'
REMOTE_PATH: '/var/www/api/v1/'
LOCAL_PATH: $BITBUCKET_CLONE_DIR

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?

 

Oleksandr Kyrdan

Hi Duncan,

Thank you for your question.

In your case use:

LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/*'

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.