Cache Pull failing, but previous Cache Push worked

Archive Issues
, ,
1

I’ve been using CachePush/Pull to cache the dependencies for my iOS build that uses Carthage. This has been working for quite a while without any issues, but today, with no changes on my side the cache pull step has stopped working, even though the previous build’s cache push worked fine.

The error it reports is:

2017/10/27 03:01:31 Cache pull…
2017/10/27 03:01:32 Failed to get download url, error: Build cache not found. Probably cache not initialised yet (first cache push initialises the cache), nothing to worry about :wink:
WARN[03:01:32] Step (cache-pull) failed, but was marked as skippable

Are there any known issues that might cause this?

1 Like
2

It appears to be working again. Perhaps just a temporary glitch? I’ll keep an eye on it.

1 Like
3

Without more info / context & log hard to say - if it’d happen again please let us know! Usually an issue like this is because something like e.g. your team mate deletes the related cache before the build could pull it. Or it might be that the cache item expired (Redirecting… - Bitrise Docs - Cache Expiring).

In any case, if you’d have any issues with the cache just let us know, with as many info as you can share and we’ll dig into it ASAP! :wink:

Happy Building!

4

Same problem exist since last 10 days with no success…

±-----------------------------------------------------------------------------+

| (2) cache-pull@2.1.3 |
±-----------------------------------------------------------------------------+
| id: cache-pull |
| version: 2.1.3 |
| collection: GitHub - bitrise-io/bitrise-steplib: New Bitrise StepLib |
| toolkit: go |
| time: 2020-01-07T09:59:48Z |
±-----------------------------------------------------------------------------+
| |
Config:

  • CacheAPIURL: [REDACTED]
  • DebugMode: false
  • StackID: osx-xcode-11.2.x

Downloading remote cache archive
Failed to get cache download url: build cache not found: probably cache not initialised yet (first cache push initialises the cache), nothing to worry about :wink:

WARN[09:59:55] Step (cache-pull@2.1.3) failed, but was marked as skippable

| |
±–±--------------------------------------------------------------±---------+
| ! | cache-pull@2.1.3 (exit code: 1) | 9.19 sec |
±–±--------------------------------------------------------------±---------+
| Issue tracker: Issues · bitrise-steplib/steps-cache-pull · GitHub |
| Source: GitHub - bitrise-steplib/steps-cache-pull: Download Cache |
±–±--------------------------------------------------------------±---------+

5

Hi there @chetan.dobariya!

Could you please send us a related build URL and enable Support Access (Enabling the Bitrise Support user for your app | Bitrise DevCenter), so that we may investigate a bit? :slight_smile:

6

Sure, here you go.

build : 67baeb1790a091ca

7

Hey there @chetan.dobariya, thanks for the build log! Could you also enable Support Access (Enabling the Bitrise Support user for your app | Bitrise DevCenter)? :slight_smile:
I’d need to confirm a few things connected to your project in order to find out the root of the issue.

8

@Roland-Bak it is enabled now :slight_smile:

9

Hey there @chetan.dobariya!

I can see that you have since managed to build your cache up, but there could be a number of reasons why the cache was:

1: someone in your org deleted the cache at one time
2: cache is related to a specific branch, which expires/is auto-deleted after 7 days if there’s no new build on that branch in the meantime . This means that if you do builds on a specific branch every day** (more frequently than a week), **it’ll never expire/won’t get deleted automatically. If you don’t start a build on that specific branch for more than 7 days, then the related cache will be removed, and your next build will run like the first time, when there was no cache for that branch yet.

10

Thanks @Roland-Bak ,

Good to know that bitrise automatically delete cached if build not happend in 7 days.

is that possible to modify this settings from user side?

11

Currently there is no feature to configure this on the user side, but if you feel that is something critical, you can always create a feature request :wink:

12

it enabled, but it always throw exception

±-----------------------------------------------------------------------------+

| (2) cache-pull@2.1.1 |
±-----------------------------------------------------------------------------+
| id: cache-pull |
| version: 2.1.1 |
| collection: GitHub - bitrise-io/bitrise-steplib: New Bitrise StepLib |
| toolkit: go |
| time: 2020-03-01T15:10:06Z |
±-----------------------------------------------------------------------------+
| |
Config:

  • CacheAPIURL: [REDACTED]
  • DebugMode: false
  • StackID:
    Downloading remote cache archive
    Failed to get cache download url: build cache not found: probably cache not initialised yet (first cache push initialises the cache), nothing to worry about :wink:
    WARN[15:10:10] Step (cache-pull@2.1.1) failed, but was marked as skippable

Please, somebody can help me how to fix it

13

Hi @thu0c_d0c!

In order to verify this being an issue, we would also need to see the previous build that pushed the cache for the same branch. Can you please create a separate issue thread about this?

14

I had the same problem. Is there any way to not expire the cache in 7 days?

15

Hi @cmonteirodialpad,

That is not possible, unfortunately.

16

I’ve scheduled a weekly build just to keep the cache… It seems to work.