I have the following pipeline-conf
- pipe: atlassian/scp-deploy:1.2.0
variables:
USER: 'hardcoded_username'
SERVER: 'hardcoded_servername'
REMOTE_PATH: '/home/xyz/client/build'
LOCAL_PATH: 'client/build/*'
DEBUG: 'true'
EXTRA_ARGS: ["-P", "12345"]
However it seems the runner is trying to connect to bitbucket.org instead of my server and than it seems to fail.
Status: Downloaded newer image for bitbucketpipelines/scp-deploy:1.2.1
DEBUG: Starting new HTTPS connection (1): bitbucket.org:443
DEBUG: https://bitbucket.org:443 "GET /bitbucketpipelines/official-pipes/raw/master/pipes.prod.json HTTP/1.1" 200 None
INFO: Configuring ssh with default ssh key.
INFO: Adding known hosts...
INFO: Appending to ssh config file private key path
INFO: Applied file permissions to ssh directory.
usage: scp [-346ABCpqrTv] [-c cipher] [-F ssh_config] [-i identity_file]
[-J destination] [-l limit] [-o ssh_option] [-P port]
[-S program] source ... target
✖ Deployment failed.
Hi @74bit .
This pipe uses under the hood scp command. Please check generated by pipe scp command: is this command correct?
Also you may try to execute it without pipe usage to understand where is the problem.
Regards, Igor
@74bit please, check this answer, maybe this is your case.
Regards, Igor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In fact, that helped me. The react-build step before did not write to the standard-dir, and the scp missed that dir in the artifact and then stopped working.
To bad there isn't any error-msg at all, like "file or directory not found"
Anyhow, thanks for your help, very much appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.