Bitbucket Pipeline SCP not setting ignoring non standard SSH port argument.

[bradcozine]

I'm trying to use an SCP deployment similar to the example given in the pipeline configurator and have it set up as follows.

script:
    - pipe: atlassian/scp-deploy:0.3.1
        variables:
            USER: 'user'
SERVER: 'XXX.XXX.116.111'
REMOTE_PATH: '$SCP_PATH'
LOCAL_PATH: 'build'
DEBUG: 'true'
EXTRA_ARGS: '-p 21098'

(Code block wont let me format the YAML)

As you can see from the log excerpt below, scp is definitely getting the port argument passed to it, however ssh is still attempting to connect over port 22.

...
scp -rp -i /opt/atlassian/pipelines/agent/ssh/id_rsa_tmp -p 21098 build user@XXX.XXX.116.111:/home/user/public_html/bitbucket/build/
ssh: connect to host XXX.XXX.116.111 port 22: Operation timed out
lost connection
✖ Deployment failed.

Any suggestions?! Thanks a bunch!

[Raul Gomis · Accepted solution]

Hey @bradcozine ,

According to the SCP docs: https://linux.die.net/man/1/scp, you need to use -P (capital letter) for specifying the port. 

This example should work:

script:
  - pipe: atlassian/scp-deploy:0.3.1
    variables:
      USER: 'ec2-user'
      SERVER: '127.0.0.1'
      REMOTE_PATH: '/var/www/build/'
      LOCAL_PATH: 'build'
      DEBUG: 'true'
      EXTRA_ARGS: '-P 8022'

Regards,

Raul

[bradcozine]

Apparently what I need are glasses. Thanks so much!