Bitbucket pipeline - publish to remote root instead of "build" folder

[Eder Wainer]

Hello there. I jut got into the Pipelines feature and Im having a hard time understanding paths. Everytime I run the pipeline below it first creates a "build" folder and then publishes all updated files inside of it. But my app was built in a way that it is very troublesome to run in inside a folder.

Is there a way to force it to publish it to the root of the ftp account?

This is the local path of my private repo:
https://coopernet@bitbucket.org/coopernet/features.git

Below is the script Im using:

pipelines:

default:

- parallel: 

- step: name: 'Build and Test'

script: - pipe: atlassian/ftp-deploy:0.3.5

variables:

USER: 'myUser'

PASSWORD: 'myPass'

SERVER: '000.00.000.00'

REMOTE_PATH: '/httpdocs/'

LOCAL_PATH: '${BITBUCKET_CLONE_DIR}'

Thanks!

[ktomk]

Sure, pushing the whole git repository into '/httpdocs/' sounds like a real security nightmare.

It is crucible to configure the FTP-upload correctly, e.g. in your case it sounds like that setting

• REMOTE_PATH: '/httpdocs/'

to a different folder is worth a try, for example if "/" expresses the root of your FTP account:

• REMOTE_PATH: '/'

If in doubt, consult your hosts support and ask about how to obtain the correct path(s).

[Theodora Boudale]

Hi @Eder Wainer and welcome to the community.

I see that you are using the ftp deploy pipe and you have defined httpdocs as REMOTE_PATH.

Just to make sure that I understand the problem correctly:

• Is the 'build' folder generated on your remote server, inside the 'httpdocs' folder?
• Do you generate a folder named 'build' anywhere in your Pipelines build?
• Do you already have a folder named 'build' in your repo?
• Does this 'build' folder on your server contain all files of $BITBUCKET_CLONE_DIR?

I can reach out to one of the developers and check whether this is expected behavior or not, I just want to make sure that I have a correct understanding of the issue first.

Kind regards,
Theodora