Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Artifact not being published in bitbucket pipeline

michalmalecki
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 17, 2019

I'm doing quite trivial java build in BitBucket Pipeline. the only twist is that it is in the repository subdirectory.

my pipeline:

pipelines:
default:
- step:
caches:
- gradle
script: # Modify the commands below to build your repository.
# You must commit the Gradle wrapper to your repository
# https://docs.gradle.org/current/userguide/gradle_wrapper.html
- bash "./foo bar/gradlew" -p "./foo bar" distTar
- ls ./foo\ bar/build -R
- echo 'THE END'
artifacts:
- ./foo bar/build/distributions/xxx.tar

 

My ls confirms that xxx.tar is in the expected location, but artifact page is empty.

....

./foo bar/build/distributions:brigitte.tar

....

2 answers

1 accepted

0 votes
Answer accepted
michalmalecki
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2019

Found it! It shoud be
- foo bar/build/distributions/brigitte.tar

artifacts paths are not real path so dot colon at the beginning was invalidating my path. Shame that it was not raised as a warning!

0 votes
Chris Witte
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 18, 2022

My issue causing artifact to be ignored was including a variable in the file name.

This fails (even though the file exists.  the variable was not resolved):

artifacts:
- "build.full/file-${BITBUCKET_BUILD_NUMBER}.iso"

This works:

artifacts:
- "build.full/*.iso"

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events