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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
....
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"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.