Why pipelines doesn't create cache?

kolya_unuchek

Here is result tree on server after my script:

> pwd
<span>/opt/atlassian/pipelines/agent/build</span>
> tree -d
<span>.<br></span><span>&#9500;&#9472;&#9472; android-sdk-linux<br></span><span>&#9474;&nbsp;&nbsp; &#9500;&#9472;&#9472; build-tools<br></span><span>&#9474;&nbsp;&nbsp; &#9474;&nbsp;&nbsp; &#9492;&#9472;&#9472; 28.0.3<br>...<br>&#9500;&#9472;&#9472; app<br>&#9474;&nbsp;&nbsp; &#9500;&#9472;&#9472; build<br>...<br>&#9492;&#9472;&#9472; readme<br></span><span>8005 directories</span>

 Here is my script:

https://opatry.net/2017/11/06/bitbucket-pipelines-for-android/

 

In result:

Build teardown
<span>You already have a 'gradle' cache so we won't create it again<br></span><span>Assembling contents of new cache 'android-sdk'</span>

 But in Pipelines -> Caches->Dependency caches :

Why pipelines didn't add `android-sdk` to cache?

mwatson

As per https://confluence.atlassian.com/bitbucket/caching-dependencies-895552876.html, the compressed cache has to be under 1GB in size to be cached - you can test this in your step's script by compressing the directory yourself and seeing how big it is. There will be a message in the tear down saying the cache is being skipped if it is too big. Additionally it is only kept for 1 week and then we expire it, to make sure it is as up to date as possible. If either of these situations don't apply to you, it might be better to raise a support requests at https://support.atlassian.com/contact/ so we can help examine your build for the cause,

Hope this helps,

Matt Watson, Bitbucket Pipelines Development Manager