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

Cache not found - single step Pipeline build

Edited

Hi folks, 

My pipeline build is unable to persist the $HOME/.cache directory across builds, hence running very slowly. Can someone find any errors in the caching setup below? 

Log message in the "Build setup" phase: 

 

Cache "mytool-cache-dir: $HOME/.cache": Downloading
Cache "mytool-cache-dir: $HOME/.cache": Not found
My Pipeline YAML simply downloads a CLI tool off the web, and runs it for a while. The network downloads fetched by the tool live in $CWD/.cache of the tool run, and should be persisted across repeat runs of the build.
image: atlassian/default-image:4

pipelines:

default:

- step:

name: 'geofeed-finder wtf'

size: 2x

caches:

- mytool-cache-dir

script:

- $HOME/bin/mytool-linux-x64 -v

- echo "Starting mytool"

- $HOME/bin/mytool-linux-x64 -c 1 -g 1 --keep-non-iso --keep-invalid-subdivisions --download-timeout 10 -o $HOME/latest.csv

- echo "Finished mytool"

- wc -l $HOME/latest.csv

artifacts: # defining the artifacts to be passed to each future step.

- $HOME/latest.csv

definitions:

caches:

mytool-cache-dir: $HOME/.cache

1 answer

1 accepted

0 votes
Answer accepted

I realized after posting this that the $PWD is not $HOME, which is my assumption in the above script. So I remove $HOME relative paths and let them be either relative to $(pwd) (present working directory) or better still the $BITBUCKET_CLONE_DIR variable. 

 

So now both the cache works and the artefacts are found correctly after the build is done. Yay!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events