port number in pipelins for deploy in FTP server in not working

[Amin Atwi]

I'm using atlassian/ftp-deploy:0.3.7 to deploy my code to a remote server.

This is my configuration into bitbucket-pipelines.yml

definitions:

    steps:

        - step: &staging-deployment

              name: Deploy to staging

              deployment: Staging

              image: node:14.15.0

              size: 2x

              caches:

                  - node

              script:

                  - pipe: atlassian/ftp-deploy:0.3.7

                    variables:

                        USER:  $user

                        PASSWORD: $STAGE_KEY

                        SERVER: $serverIP

                        REMOTE_PATH: /www/wwwtravizorycom_857/public/

                        DEBUG: "true"

                        EXTRA_ARGS: "-p 58609"

I'm trying to add the port number in EXTRA_ARGS

based on this documentation 

https://manpages.ubuntu.com/manpages/trusty/en/man1/lftp.1.html

I can add the port number by using "-p portNumber".

The problem is that the port number is been added at the end of the LOCAL_PATH instead of the SERVER. 

Any ideas?

[Ben · Accepted solution]

Hey Amin,

I've noticed that you have not yet received a reply from our Community so I figured I would jump in.

Have you tried to specify the port number within the server address itself in the $serverIp variable?
For instance:
{code}
SERVER: 127.0.0.1:21
{code}

I would also ensure that you make sure that at the server side, the following IP addresses are whitelisted:
https://support.atlassian.com/bitbucket-cloud/docs/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall/

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)

[Amin Atwi]

Hey @Ben ,

for some reason whether adding the port number in $serverIp or not, I'm always finding ":" at the end of the $serverIp variable

for example

I'm not adding ":", for some reason it keeps showing at the end of the $serverIP

any ideas why that is happening?

regards,

[Ben]

Hey Amin,

There's a chance that the variable has not been configured correctly or it is pulling the data from elsewhere and getting confused.

We will need to troubleshoot each element here, I'd suggest trying the following scenarios:

1. Try manually entering the SERVER field without making use of the variable and see if this makes any difference
2. Try entering the SERVER field without variable using the hostname rather than the IP address, try this with both the port number appended to the server address and with the "-P' in the args section seperately

Cheers!

- Ben (Bitbucket Cloud Support)

[Anthony Kolka]

I am having this exact same issue with the same module, so it's easily reproducible. I added some exclusion args and they don't end up in the path, only the port number does.

EXTRA_ARGS: '-p 455 --exclude=.gitignore --exclude=.git/ --exclude=.vscode/'
LOCAL_PATH: $BITBUCKET_CLONE_DIR
REMOTE_PATH: '/'

[Amin Atwi]

Hey @Ben ,

finally, it worked

I'm using atlassian/ftp-deploy:0.3.7  to deploy into KINSTA

based on this documentation SFTP with Kinsta , KINSTA only supports SFTP connections to ensure your data remains safe and encrypted

so I switch to atlassian/sftp-deploy:0.5.7 after adding the proper configuration it worked.

My bitbucket pipeline file looks like this

image: atlassian/default-image:3

options:

  docker: true

  size: 2x

definitions:

    services:

        docker:

            memory: 2048 #increasing docker service memory

steps:

        - step: &staging-deployment

              name: Deploy to staging

              deployment: Staging

              image: node:14.15.0

              size: 2x

              caches:

                  - node

              script:

                  - cd wp-content/themes/travizory

                  - npm install

                  - npm run build

                  - rm -rf node_modules

                  - cd ../../../

                  - pipe: atlassian/sftp-deploy:0.5.7

                    variables:

                      USER: '${STAGE_User}'

                      PASSWORD: '${STAGE_KEY}'

                      SERVER: '111.111.111.111'

                      REMOTE_PATH: '/www/wwwtravizorycom_857/public/'

                      LOCAL_PATH: '${BITBUCKET_CLONE_DIR}'

                      DEBUG: 'false'

                      EXTRA_ARGS: '-P 57631'

pipelines:
custom:

staging-deployment:
- step: *staging-deployment

Regarding the PORT number,

it's normal to look like this in the bitbucket pipeline.

@Anthony Kolka you need to make sure to pass the port number like that :

EXTRA_ARGS: '-P 57631'

@Anthony Kolka If you have any questions don't hesitate to ask me.

Regards,

[Anthony Kolka]

How would we also disable the hardcoded refusal to use SSL and add 

ssl:verify-certificate no

instead?

[Anthony Kolka]

Also, how can you override the hardcoded delete first flag? Not all deployments call for wiping out what exists.

[Anthony Kolka]

Delete please