Consider this snippet from a pipeline definition:
- pipe: sonarsource/sonarcloud-scan:1.0.1
The `sonarcloud-scan` pipe downloads language analyzers and plugins from SonarCloud, which are used to analyze the source code. These files are not small, and there are many of them, so downloading takes non-trival amount of time. On every execution, the scanner looks at the cache directory, and only downloads files that have changed since the last run. And they don't change very often, so a good candidate for caching.
The `caches` definition in the above snippet works fine when running the scanner in the pipeline. But not when running the pipe (which inside of it runs the scanner).
Looking at the output of the pipe, in the argument list of the `docker` command I don't see values like `--volume=...` related to caches, so it seems to me the defined cache is not available to the pipe.
Can you please confirm that:
Hi @janos-ss ,
Thanks for the suggestion. At the moment, we don't natively support caching in pipes. We created a feature request to gauge the interest of others in seeing the same thing: https://jira.atlassian.com/browse/BCLOUD-18478 I would recommend to comment and vote for it, so that we can prioritise it properly.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events