Exploring pipeline caching on Azure and it’s shortcomings
In late 2019, Azure DevOps finally released a feature to enable caching on pipelines. Pipeline caching on other platforms like AWS, Bitbucket is pretty straightforward and works like a charm.
Pipeline caching on Azure is slightly different and I’d say it’s still a work in progress. This means on some occasions it might not work as expected.
This article will explain how pipeline caching works on Azure DevOps and address the gotchas.
Cache@2 Task
This task has 3 input arguments -
- key (required): unique key to identify the cache
- path (required): path of the folder or file you want to cache
- restoreKeys (optional): If key fails, this will be the fallback to find cache