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
I can not cache ssh-run, what do I do wrong?
.- step:name: Cache-testingcaches:- ssh-runartifacts:download: falsescript:- pipe: atlassian/ssh-run:0.4.0variables:SSH_USER: "test-admin"SERVER: "00.00.0.00"MODE: "command"COMMAND: 'echo "it should be cached now???"'definitions:caches:ssh-run: ssh-run/
Hi @serhatakbak and welcome to the community!
You can define a cache for the Docker image of the pipe atlassian/ssh-run. In order to do this, you need to define a docker service for the step and also caches: docker.
I have modified your step below to show how it should be defined:
- pipe: atlassian/ssh-run:0.4.0
COMMAND: 'some command?'
The cache will be saved after the first successful build and will be used in any subsequent builds up until a week. Any cache which is older than 1 week will be cleared automatically and repopulated during the next successful build.
Please feel free to let me know if this works for you and if you have any questions.
Are you using atlassian/default-image as a build container for your steps?
If so, we are caching public Docker images, including atlassian/default-image, so a cache is used when a public Docker image is used as a build container. No configuration needs to be made by end-users for that purpose.
If I correctly understand `caches` then I think they are only useable when the image can have dependencies not being included in the current files, as with nodejs (npm install) and dotnet (dotnet restore).
So ssh-run is dependency free therefore no caches.