Pull Pipeline intermediate files
The Step downloads Pipeline intermediate files to a local folder.
The Step downloads Pipeline intermediate files to a local folder.
The Step downloads Pipeline intermediate files to a local folder. These intermediate files are generated by Workflows in a Pipeline intended to be shared with subsequent Workflows.
Make sure to add this Step after you have uploaded the intermediate files. You can upload the intermediate files using the Deploy to Bitrise.io Step's Files to share between Pipeline Workflows input. The directories you specify will be archived and uploaded as a single file.
When uploading the Pipeline intermediate files, you must assign environment variable keys to them in the Files to share between Pipeline Workflows input. After downloading the files, the environment variable key will point to the file's local path.
When downloading a file, that was a directory originally, they are extracted, and the specified environment variable will point to the directory's local path.
By default, all files shared by any Workflow of the Pipeline are downloaded. This can be limited by setting the Intermediate file source input.
Please note that this step is designed to be executed on the CI only.
To configure the Step:
NOTE: You can list multiple Workflows by separating them using a comma. For example: {workflow1},{workflow2}
true if you want to log additional information for debugging purposes.A step to retrieve your cache from a S3 bucket using custom keys with fallback. This should be used with the s3-cache-push step to store the cache. If you want to retrieve multiple items, you'll need run this step multiple times. Bucket Access For this step to work you'll need an user in aws with programmatic access to a bucket. The user should have permissions to list, get, and put objects in the bucket. You can set the credentials using the Bitrise Secrets with the keys specified in the inputs or set them directly in the inputs.
