icon

Bitrise.io Cache:Pull

Download the build cache from bitrise.io.

⚠️   The branch-based caching steps are deprecated and being replaced by key-based caching. Check out our migration guide: [Migrating from branch-based caching to key-based caching](https://devcenter.bitrise.io/en/dependencies-and-caching/branch-based-caching/migrating-from-branch-based-caching-to-key-based-caching.html).

Downloads the build cache from bitrise.io, and moves the files back to their original place. The aim is to speed up your builds as not having to download every single dependency every time can be a serious timesaver.

Configuring the Step

To be able to pull from a previous build's cache, you need two things.

  1. The Cache:Push Step at the end of your Workflow.
  2. At least one successful build on the same branch in the last seven days.

If there was no successful build on the branch in question in the last seven days, the cache automatically gets deleted.

Troubleshooting

If the Step fails, check the time of the latest build. If there was a successful build in the last seven days, check if the Workflow included the Cache:Push Step.

If the Cache:Push Step was present, check the inputs of the Step. It's possible, for example, that the provided cache path is incorrect.

Useful links

Related Steps

Similar steps

Deploys build artifacts to make them available for the user on the build's Artifacts tab. Sends test results to the Test Reports (build's Tests tab). Uploads Pipeline intermediate files to make them available in subsequent Workflows and also uploads Bitrise and user generated html reports.

Activates Bitrise Remote Build Cache for subsequent Bazel builds in the workflows.

Activates Bitrise Remote Build Cache add-on for subsequent Gradle builds in the workflow

Activates Bitrise Build Cache features for React Native projects