The Cache:Push Step takes over 20 minutes to complete.
There are several reasons this could happen. Several possible causes are listed below. Please review those relevant to your situation.
Exceptional large number of files or a large number of files
Your cache may contain an exceptionally large file, or an exceptionally large number of files. Download your build cache to investigate.
- On the app page, click the "Settings" tab.
- Click the "Manage Cache" button.
- Download your build cache.
Once you've downloaded the cache file, extract the files to investigate. Remove unnecessary files and/or reduce size of file(s) if possible.
While uncommon, your cache may be misaligned with your build requirements. This occasionally happens when a new version of the Cache:Push Step is released. Delete the cache file and allow it to be regenerated.
Attempting to cache CocoaPods
The Run CocoaPods install Step has built-in caching that is enabled by default. If you wish to cache CocoaPods, you should leave this enabled, You should not add the CocoaPods directory in the Cache:Push Step.
Attempting to cache Maven
Do not attempt to cache Maven by adding paths to the Cache:Push Step. To cache Maven, make sure your Workflow contains the Cache:Pull Step after the Git Clone Step and before your Android Build Step. You should have the Cache:Push Step at the end of your Workflow.
Attempting to cache Gradle
Do not attempt to cache Gradle by adding paths to the Cache:Push Step. To cache Gradle, make sure your Workflow contains the Cache:Pull Step after the Git Clone Step and before your Android Build Step. You should have the Cache:Push Step at the end of your Workflow.