It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
caches:
- node
script:
- cd front-end
- npm install
- npm i gulp -g
- gulp build --production
artifacts:
- public/dist/**
- step:
name: Deploy Repository files using SCP to Staging
deployment: staging
script:
- pipe: atlassian/scp-deploy:0.3.12
variables:
USER: '$DEPLOY_USER'
SERVER: '$DEPLOY_HOST'
REMOTE_PATH: '$DEPLOY_PATH_STAGING'
LOCAL_PATH: '$BITBUCKET_CLONE_DIR/'
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
Alex

1 answer

0 votes
Jimmy Seddon Community Leader 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: 
https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/

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!

-Jimmy

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

1,590 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you