Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


No Artifacts Upload during Build Step

Hi everyone,

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:

- step:
name: Build
image: node:10.16.0
- node
- cd front-end
- npm install
- npm i gulp -g
- gulp build --production
- public/dist/**
- step:
name: Deploy Repository files using SCP to Staging
deployment: staging
- pipe: atlassian/scp-deploy:0.3.12
DEBUG: 'true'

This is the output
Bildschirmfoto 2020-09-16 um 16.46.45.png
What am I missing that my Build step can't seem to be able to upload artifacts?
Any ideas?

Best regards

1 answer

0 votes
Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 16, 2020

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 BITBUCKET_CLONE_DIR."

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!


@Alex Nowak were you able to find a solution for this? I am also facing the same issue. Target folder has the artifacts but they are not being uploaded to the artifacts tab to be able to use them in next steps. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events