Skip to content
Upload Cache
Branch: master
Clone or download
lpusok and godrei Adding cache info file to archive, which includes stack ID (#27)
* Adding cache info file to archive, which includes stack ID

* Rename stackVersions to stackVersionData

* Removing type fields from test as is unused, use time.Since instead of time.Now().Sub

* dep update

* Use path under /tmp for archive_info.json

* Repository path migration, dep update
Latest commit 43d9deb May 16, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
vendor/github.com Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
.gitignore
CHANGELOG.md v2.0.5 Jan 31, 2018
Gopkg.lock Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
Gopkg.toml Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
LICENSE Initial commit Mar 25, 2016
README.md TODO: CI Apr 4, 2016
bitrise.yml Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
cache_archive.go Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
cache_archive_test.go Step revision (#22) Mar 20, 2019
cache_descriptor.go Step revision (#22) Mar 20, 2019
cache_descriptor_test.go Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
cache_path.go Step revision (#22) Mar 20, 2019
cache_path_test.go Step revision (#22) Mar 20, 2019
config.go Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
gows.yml Changed caching method (#11) Sep 25, 2017
main.go Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
release_config.yml Prepare for 1.1.2 Jul 4, 2017
stack_info.go Adding cache info file to archive, which includes stack ID (#27) May 16, 2019
step.sh fingerprints fix (#9) Jul 4, 2017
step.yml Step revision (#22) Mar 20, 2019

README.md

Cache Upload

This step implements Cache Upload for bitrise.io.

TODO

  • CI
  • Unit Tests

How to use this Step

Can be run directly with the bitrise CLI, just git clone this repository, cd into it's folder in your Terminal/Command Line and call bitrise run test.

Check the bitrise.yml file for required inputs which have to be added to your .bitrise.secrets.yml file!

Step by step:

  1. Open up your Terminal / Command Line
  2. git clone the repository
  3. cd into the directory of the step (the one you just git cloned)
  4. Create a .bitrise.secrets.yml file in the same directory of bitrise.yml - the .bitrise.secrets.yml is a git ignored file, you can store your secrets in
  5. Check the bitrise.yml file for any secret you should set in .bitrise.secrets.yml
  • Best practice is to mark these options with something like # define these in your .bitrise.secrets.yml, in the app:envs section.
  1. Once you have all the required secret parameters in your .bitrise.secrets.yml you can just run this step with the bitrise CLI: bitrise run test

An example .bitrise.secrets.yml file:

envs:
- A_SECRET_PARAM_ONE: the value for secret one
- A_SECRET_PARAM_TWO: the value for secret two

How to create your own step

  1. Create a new git repository for your step (don't fork the step template, create a new repository)
  2. Copy the step template files into your repository
  3. Fill the step.sh with your functionality
  4. Wire out your inputs to step.yml (inputs section)
  5. Fill out the other parts of the step.yml too
  6. Provide test values for the inputs in the bitrise.yml
  7. Run your step with bitrise run test - if it works, you're ready

NOTE:

If you want to use your step in your project's bitrise.yml:

  1. git push the step into it's repository
  2. reference it in your bitrise.yml with the git::PUBLIC-GIT-CLONE-URL@BRANCH step reference style:
- git::https://github.com/user/my-step.git@branch:
   title: My step
   inputs:
   - my_input_1: "my value 1"
   - my_input_2: "my value 2"

You can find more examples of step reference styles in the bitrise CLI repository.

How to contribute to this Step

  1. Fork this repository
  2. git clone it
  3. Create a branch you'll work on
  4. To use/test the step just follow the How to use this Step section
  5. Do the changes you want to
  6. Run/test the step before sending your contribution
  • You can also test the step in your bitrise project, either on your Mac or on bitrise.io
  • You just have to replace the step ID in your project's bitrise.yml with either a relative path, or with a git URL format
  • (relative) path format: instead of - original-step-id: use - path::./relative/path/of/script/on/your/Mac:
  • direct git URL format: instead of - original-step-id: use - git::https://github.com/user/step.git@branch:
  • You can find more example of alternative step referencing at: https://github.com/bitrise-io/bitrise/blob/master/_examples/tutorials/steps-and-workflows/bitrise.yml
  1. Once you're done just commit your changes & create a Pull Request

Share your own Step

You can share your Step or step version with the bitrise CLI. Just run bitrise share and follow the guide it prints.

You can’t perform that action at this time.