Skip to main content

Dedicated caching Steps for dependency managers

Abstract

Bitrise's dedicated caching Steps store their archives in the same storage space as the Save cache and Restore cache Steps but unlike those two, they automatically set up the appropriate cache paths and cache keys and as such, they require no configuration.

Key-based caching is powerful and flexible: you can use the Save cache and Restore cache Steps with any app, regardless of platform or the type of data you want to cache. However, these Steps require careful configuration and it is possible to make mistakes. If you are looking for a simple solution to cache dependencies of the most frequently used dependency managers, we offer dedicated Steps that require no configuration whatsoever.

The dedicated caching Steps store their archives in the same storage space as the Save cache and Restore cache Steps but unlike those two, they automatically set up the appropriate cache paths and cache keys.

The following dedicated Steps are available:

To use these Steps, simply add the Restore version to the start of your Workflow and the Save version to the end of your Workflow. No other configuration is needed.

In this section:

A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.

app

A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.