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,464,242
Community Members
 
Community Events
176
Community Groups

Artifact not being published in bitbucket pipeline

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

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!

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

Atlassian Community Events