Bitbucket Runner - sftp-deploy

[Renato Baudouin]

sftp-deploy:0.5.7

Hello Comunity, I am trying to deploy to on-premise via Runner using the sftp-deploy. In the figure 1 you can find the deployment yaml. The figure 2 shows the deployment logs. It seems to be running ok beacuse it donwloads the "sftp-deploy:0.5.7" image, stablish the connection with the remote host but it its not enable to stablish the sftp connection beacuse of the host key verification.

At this point, I am not pretty sure how to pass to the image the known_hosts. I tried to use the SSH_KEY configuration, but it seems that it does not fecht the Fingerprints via runners.

Does any of you have an idea to work this out?

Figure 1 - Deployment yaml

Figure 2 - Deployment logs

[Renato Baudouin · Accepted solution]

At the end I decided to stop using the image: "atlassian/sftp-deploy:0.5.7" and copy the artifact using sshpass using the image: "atlassian/default-image:latest". Here is the final pipeline:

[hitesh-makwana]

Hi Renato,

Thank you so much. I was having sftp issue for fresh deployment with

atlassian/sftp-deploy:0.5.8. I searched a lot and tried everything but didn't work. Able to deploy files but not folder which doesn't already exist on server. Finally able to do that with ssh.

[Renato Baudouin]

You are welcome :). Glad it helps you.

[Viktoras Domarkas]

Hi Renato,

If you still have problems you can use the tutorial I followed when creating the pipeline: https://www.youtube.com/watch?v=OCA_jB1Dw0I 

The part that you need starts at 13:23

[Timothy Gonzalez]

Excellent video. To provide the answer on this post the solution was to go to Repository Settings -> SSH Keys then under known hosts enter the domain/ip of the server you are trying to connect to, get the finger print, then add the host.

[Caroline R]

Hi, @Renato Baudouin! 

Thank you for reaching out to Atlassian Community!

In order to further investigate this issue, could you please confirm:

1. What is the Runner version you are using? You can find it in the Runner log on the top. 

2. Have you fetched the host fingerprints in the Pipeline?

Thank you.

Kind regards,
Caroline

[Renato Baudouin]

Hi Caroline,

Thank you for your response.

Here are my comments:

1. What is the Runner version you are using?  It is Runner version: 1.174, Runner runtime: linux-docker

2. Have you fetched the host fingerprints in the Pipeline? I am not sure how to do it. I tried to user the SSH_KEY in the repository settings, but it seems that it does not fecht the Fingerprints via runners.

[Caroline R]

Hi, Renato. 

Thanks for the information. It seems your Runner is not updated, so first of all, you need to upgrade the Runner version that has some bug fixes and some enhancements.

You can check in the following link how to update the runner:

• https://support.atlassian.com/bitbucket-cloud/docs/troubleshooting-runners/#Updating-a-runner-version

Also, by your last comment, I couldn’t understand if you have fetched the host fingerprints in the Pipelines setting. So, in case you haven’t, please follow the next steps to accomplish that: 

• Open your repository in Bitbucket

• Click on Repository settings

• Under the Pipelines section, open SSH keys 

• There, you can add the known hosts and fetch the fingerprints

Please, feel free to share any additional questions or concerns regarding this case. 

Kind regards,
Caroline

[Renato Baudouin]

Hi Caroline,

Thank you very much for your response. Yes, I tried to configure the known hosts the in the SSH key. But it is no able to fetch it, because my Remote Host is onPremise. Please check the Figure 3. So here is my questions:

• Is there a way to indicate that the fetch should be made through the runner?

Figure 3 - Diagram

 

[Caroline R]

Hi, Renato! 

Thank you for the additional information! In this case, you can add it in the Pipeline YML:

ssh-keyscan -p 20 -t rsa <Host URL> >> /.ssh/known_hosts

It should add the fingerprint. Please let me know how it goes and don't hesitate to ask for any further information if needed. 

Kind regards,
Caroline

[Renato Baudouin]

Hi Caroline,

I put the ssh-keyscan statement in the script section as shown in the Figure 1. But it seems that I still have a failed deployment. 

Figuere 1 - YML

Figure 2 - Log Error

[Caroline R]

Hi, Renato!

Thanks for sharing the logs. I see that there is a code 6 there, which means "File does not exist". You have specified LOCAL_PATH, however, I don’t see any steps about the file generation.

In this case, could you please verify the file mentioned in the LOCAL_PATH variable? You can run the following command before the pipe to confirm if the directory exists and if there is something in it:

ls -lah 

Thank you. 

Kind regards,
Caroline

[Renato Baudouin]

Hi Caroline, you where rigth. I didn't check the correct path for the artifact. I verified that it downloads the artifact to this path: "/opt/atlassian/pipelines/agent/". I correct it but neithet i could make it work. At the end I decided to stop using the image:  "atlassian/sftp-deploy:0.5.7" and copy the artifact using sshpass.

[Renato Baudouin]

By the way thank you very much for your assistance :)