Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,654
Community Members
 
Community Events
176
Community Groups

scp-deploy pipe needs documentation on LOCAL_PATH, and ${BITBUCKET_CLONE_DIR}

Edited

The documentation on scp-deploy needs clarification on the LOCAL_PATH variable. Right now it is very unclear as to what path this is actually referring to, and what to set it to in order to copy the contents of the repo.

The default shown in the docs is:

LOCAL_PATH: 'build'

or

LOCAL_PATH: 'build/*'

This might lead one to believe that the pipelines docker is creating a build directory, which is not the case. You'll get:

build/*: No such file or directory

From there, one might think, well then let me put in:

LOCAL_PATH: '/*'  ##'DO NOT DO THIS!'

to copy from the root of my repo's directory. This will actually start copying all of the root system files from the docker itself! Yikes! It should be specified that this root is actually the root of the system itself in the docker container.

From there, I can't tell where the repo directory is from the docs. I found this Atlassian Community question which mentioned the default variable BITBUCKET_CLONE_DIR. Which stands for:

"The absolute path of the directory that the repository is cloned into within the Docker container."

So based on the answer to that question, and the docs, it looks like a default example to copy from the repo (only files, not the directory itself) should either be:

LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/*'

or

LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/'

?

The first appears to work, though the SCP command that appears in the docker log shows an extra slash in the remote path to the file being copy after the repo name (repo-name//file-name.txt). So something needs to change with LOCAL_PATH, or possibly REMOTE_PATH should not have a slash at the end as documented.

 

 

1 answer

1 accepted

1 vote
Answer accepted

Hi @tipjosh ,

Thank you for your detailed feedback!

New SCP Deploy pipe's version with updated documentation is released (scp-deploy:0.3.9).

 

Cheers,
Alex

Excellent. Thank you for the clarification.

Like Oleksandr Kyrdan likes this

Hi @Pavel Alazankin ,

Great suggestion! Thank you!

 

Cheers,
Oleksandr Kyrdan

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events