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

Your Points Tracker
  • 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
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?
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

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

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

- step:
- pipe: atlassian/scp-deploy:0.3.3
USER: '<username>'
SERVER: '<ip addr>'
REMOTE_PATH: '/var/www/api/v1/'

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?


1 answer

1 accepted

1 vote
Answer accepted

Hi Duncan,

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.

Thanks! That looks like it copies the correct files, but they all have 777 permissions on the remote machine. Is there something else I need to do to specify the target permissions?

Like # people like this

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.

Like # people like this

It would be good to have this on the pipeline information screen (on the screen when adding a new pipeline)

Like mkarthauser likes this

The problem is the trailing asterisk symbol (*) in the LOCAL_PATH variable leads to the fact that hidden files will not be copied (any files starting with "." - .htaccess, .env, etc). It is a general Linux behavior, but it would be nice to have some way to copy the hidden files and don't have a "build" directory on the server.

I found a solution: just use atlassian/rsync-deploy  and a slash at the end of LOCAL_PATH. Then hidden files will be copied and "build" dir will not be created.

- pipe: atlassian/rsync-deploy:0.4.4

Suggest an answer

Log in or Sign up to answer
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...

670 views 15 9
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