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
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
We have a monorepo that contains about 5 projects. All these projects are build based on the git change history, so if project A is not changed, it is not build. This is al managed by Nx monorepo.
e want to split every deploy into its own step so that we have more control over each project's deployment.
In order to achieve this we need to change our build step so that it only executes if the dist folder contains the portal it is ment to deploy. I've read about the condition configuration, but i cannot find anything about checking build artifacts in a condition instead of the git commit that triggerd the change. So is there a way to skip (or directly pass) a step if the portal is not in the build artifact?
- step: &build
- git fetch origin master:refs/remotes/master
- npm run build
Example Dist artifact
│ ├── login-portal
│ ├── Portal-Y
Our deploy step
- step: &deployLoginPortal
- aws s3 sync $LOGIN_OUTPUT_PATH s3://$LOGIN_S3_BUCKET/ --acl public-read # Sync the portal
# $LOGIN_OUTPUT_PATH = 'dist/login-portal'
Example condition (does not work)
- $LOGIN_OUTPUT_PATH/** # only run if dist contains changes in $LOGIN_BUILD_PATH
How can I check the build artifact if a specific path exists so that I can execute or skip the build step?
as theres no out of the box solution from atlassian, what i did was something like:
if something exists; then
echo true > condition.txt
if $(cat condition.txt); then
- do stuff
Thank you for contacting Atlassian Community, my name is Norbert and I'm a Bitbucket Cloud Support Engineer, it's nice to meet with you! Welcome to the Atlassian Community.
I would like to inform you that the functionality what you're looking for is unfortunately not available. The conditionsets configuration ONLY checks the content of the commit.
For example if you commit a change to your repository and the change is located in the "includePaths" location, a build will be triggered, but unfortunately we yet to have the feature which checks for artifacts.
Atlassian Bitbucket Cloud Support