You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I created a bitbucket-pipelines.yml file and added a step in order to build frontend assets before transfering files to a server.
I cannot use rsync (pls don't ask why or recommend me using it. I just can't) and instead use scp.
But the problem lies within my build step, because it doesn't seem to upload artifacts which I then can transfer on my remote host system.
Here is a snippet of my pipelines file:
- cd front-end
- npm install
- npm i gulp -g
- gulp build --production
name: Deploy Repository files using SCP to Staging
- pipe: atlassian/scp-deploy:0.3.12
This is the output
What am I missing that my Build step can't seem to be able to upload artifacts?
Hi @Alex Nowak,
Welcome to the Community!
I'll admit that I'm not 100% familiar with BitBucket Pipelines as our company uses a Bamboo server. However, we do use YAML specs for our build plan configurations and a number of things look similar.
Looking at the documentation for pipeline artifacts here:
I see the statement: "Artifact paths are relative to the
I know when I have been setting things up myself, this can be the bane of my existence as well. My first thought would be to check and make sure that "- public/dist/**"
Is actually the relative path you are expecting to get artifacts from. You could also test this by adding a second definition for a file that you know will exist in the root of the
BITBUCKET_CLONE_DIR just to make sure that artifacts are actually being discovered and saved as a part of the build step.
Those would be the spots I'd start looking fist.
I hope that helps!