Step source env var and update command in CLI

If you use our CLI, you need to know about these two new features rolled out in this month's update.

If you use our CLI, you need to know about these two cool new features rolled out in this month's update. (Check out all the details here.)

New Bitrise CLI command: update

Whether you’ve installed it from brew or from the GitHub release, you’ll be able to call “bitrise update” now, and it will update the CLI to the latest version. If you have installed the CLI from the GitHub release, then you can select the version you want to update/or downgrade to. The CLI will check once every day and notify you as soon as there is a new version out there!

New environment variable exported by the CLI automatically: BITRISE_STEP_SOURCE_DIR

If you need to keep a binary, assets or anything else required for your step that need(s) to be bundled in the step repo, then you can include it beside your step.yml and step code, as now you will be able to access those files using BITRISE_STEP_SOURCE_DIR.

For example: $BITRISE_STEP_SOURCE_DIR/mytool.jar

Happy building!

No items found.
The Mobile DevOps Newsletter

Explore more topics

App development

Best practices from engineers on how to use Bitrise to build better apps, faster.

Community

Meet other Bitrise engineers, technology experts, power users, partners and join our BUGs.

Company

All the updates about Bitrise events, sponsorships, employees, and more.

Insights

Mobile development, latest tech, industry insights, and interviews with experts.

Mobile DevOps

Learn why mobile development is unique and requires a set of unique practices.

Releases

Stay tuned for the last updates, new features, and product improvements.

The Mobile DevOps Newsletter

Join 1000s of your peers. Sign up to receive Mobile DevOps tips, news, and best practice guides once every two weeks.