What is the easiest way to deploy an bitbucket pipeline artifacts to a remote server

Question

I have been looking at the documentation most of the documentation explains.

Here are my requirements

1. java project

2. pipeline uses custom image (with ssh installed)

3. create artifact jar, ear or whatever

4. Deploy that artifact to a remote servers (QA, TST and PROD) via ssh.

step 4 is where I am struggling with. Followed this document but I am struck at Step 2: Update the known hosts while I get an error as "unable to fetch fingerprints ....."

I am unsure of step 3 should I be adding known hosts file to the remote server or my custom docker image. I believe its remote server but then how does my custom docker image talk to the remote host?

Is there any documentation on of easy way to deploy the artifact to a remote server.

Theodora Boudale · Answer

Hi @Srikanth Mamidala, Thanks for your patience as we've been looking into this. It should actually be possible to deploy to one of your local machines that doesn't have access to the internet with the scp-deploy pipe, using a jumpbox. * You will need to add the Pipelines public SSH key to the authorized_keys of both the jump server and the machine you will be deploying to * You will need to add the address of the jump server in the 'Known hosts' of the repo (in the page Repository settings > SSH keys) The pipe should then be configured as follows: pipelines: default: - step: script: - pipe: atlassian/scp-deploy:1.1.0 variables: USER: SERVER: REMOTE_PATH: LOCAL_PATH: '*' DEBUG: 'true' EXTRA_ARGS: ['-o', 'ProxyJump :', '-o', 'StrictHostKeyChecking=no', '-o UserKnownHostsFile=/dev/null'] So this is possible by using the ProxyJump argument of the scp command, and also by using the options 'StrictHostKeyChecking=no' and '-o UserKnownHostsFile=/dev/null'. You need to also make sure that the jump server can communicate with the local machine you want to deploy to. Some other suggestions we can make apart from the above setup: - You can use a proxy server, deploy there with the pipe, and configure the proxy server to redirect the traffic to one of the machines in your local network - You can also explore using Bitbucket Pipelines Runners, which can be run in your own network infrastructure and run your deployment there: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Runners-is-now-in-open-beta/ba-p/1691022 Kind regards, Theodora

Theodora Boudale · Answer

Hi @Srikanth Mamidala, please allow me to check with my team regarding your last question and I'll get back to you on that.

Srikanth Mamidala · Answer

Got it thank you. But there may be use cases similar to mine for others as well, whats the ideal Atlassian suggested workaround for these situations? Use a jump box or something? if use a jumpbox which pipe would support that