Carthage is not using the cache on Travis at each build stage about swiftframeworktemplate

[rahul0x24]

If your repository is public, can you post the link to the travis-job. I will need to investigate more into this but if you think it will improve timings, then I am happy to review your PR.

Thanks

[rahul0x24]

@gobetti Cache seems to work fine with a library which was created with this template - https://travis-ci.org/Restofire/Restofire/jobs/378606026 (line 2900-2902). So I think, It creates individual cache per stage.

Closing this issue for now.

[gobetti]

Sure! Here is build #1: https://travis-ci.org/gobetti/RxCocoaNetworking/builds/384253067
I would expect it to build all Carthage dependencies on #1.1 only but then #1.2 did it too and #1.3 was also doing it when I cancelled the build.
Then I made that change I mentioned in the OP and started build #2: https://travis-ci.org/gobetti/RxCocoaNetworking/builds/384426851
This time, both #2.1 and #2.2 seemed to reuse correctly the cache from build #1, but #2.3 started to build the Carthage dependencies and I cancelled it.

I see you closed this issue because we share the belief that the cache is done per stage instead of per build, but isn't there a way to have it per build? Otherwise, even though a stage is only meant for iOS, it will build tvOS, macOS, watchOS... and everything again in the next stage.

[gobetti]

I'll test https://docs.travis-ci.com/user/build-stages/warm-cache/ and let you know

[rahul0x24]

Yes, For the first run, it takes a lot longer than expected and it reduces to 4 secs from next builds. It would be great to even reduce the time on the first run. I will investigate a little more but will give this less priority over others.

I appreciate your contribution and happy to review if you find a solution.

[gobetti]

The prepare cache stage suggested by Travis doesn't seem to work: https://travis-ci.org/gobetti/RxCocoaNetworking/builds/384454891
That stage itself was able to use the existent cache, and then the jobs on the next stage that had run on previous builds also used the cache, but once it runs a job that hadn't run before, again it says it couldn't find anything cached for Carthage :(

I'll probably give up on Travis and move to Circle which seems to be what the community is doing

[rahul0x24]

Circle ci is also good but it is not free for macOS containers and I don't see this as a big issue right now as all the subsequent builds use caches and time is decreased drastically. It's not something to invest a lot of time at.

Closing it for now 👍🏻. Thanks

[gobetti]

It's fine to keep it closed, I think we'll be able to do something about it once travis-ci/travis-build#1265 is merged