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.
The following step is skipped even though there is a change, on no logs to display:
clear-cache: &clear-cache-if-needed
name: "Clear cache if dependency changed"
script:
- pipe: atlassian/bitbucket-clear-cache:3.1.1
variables:
BITBUCKET_USERNAME: $BITBUCKET_USERNAME
BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD
CACHES: ["node"]
DEBUG: "true"
condition:
changesets:
includePaths:
# only if package.json file has changed
- 'package.json'
2 days ago it was working perfectly.
Now:
Welcome to the community.
Would it be possible for you to confirm if the change from the 2nd build is from the file package.json?
You can go to the Pipelines build and click the commit hash to review the file(s) changes.
Regards,
Mark C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that.
Btw, is it a push or pull-request trigger?
Regards,
Mark C
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.
Hi @Jefferson Xavier
Thanks for that info.
When the Pipelines build is triggered by the pull request, is it a merged PR or just a typical PR update?
This is for me to test the scenario on my end.
Regards,
Mark C
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.