Skip to content

Latest commit

 

History

History
26 lines (19 loc) · 1.13 KB

README.md

File metadata and controls

26 lines (19 loc) · 1.13 KB

S3 Cache Push

A bitrise step to store your cache in a s3 bucket with custom keys.

Should be used with S3 Cache Pull

Inputs

Input Description
cache_aws_access_key_id Your aws access key id
cache_aws_secret_access_key Your aws secret access key
cache_aws_region The region of your S3 bucket. E.g.: us-east-1
cache_bucket_name The name of your S3 bucket. E.g.: mybucket
cache_path The path to the file or folder you want to cache. E.g.: ./Carthage/Build
cache_key The key that will be used to restore the cache later. E.g.: carthage-{{ branch }}-{{ checksum "Cartfile.resolved" }}

Cache Key

The cache key can contain special values for convenience.

Value Description
{{ branch }} The current branch being built. It will use the $BITRISE_GIT_BRANCH environment var.
{{ checksum "path/to/file" }} A SHA256 hash of the given file's contents. Good candidates are dependency manifests, such as Gemfile.lock, Carthage.resolved, and Mintfile.
{{ stackrev }} The machine's stack id. It will use th $BITRISE_OSX_STACK_REV_ID environment var.