From @viktorbenei on Tue Nov 10 2015 09:51:32 GMT-0500 (EST) Assign the value of one env to another one (Step outputs are just regular Environment Variables) Ex: if different tools use different envs for the same thing, like ipa path Something simple like: #!/bin/bash set -e source_env_value="…

Set environment variable step is now available, thanks to @kdobmayer :tada: [image] Step Set environment variable v0.9.1 Changelog We released a new version ( 0.9.1 ) of Set environment variable step. Changes: Fix typo in title [image] GitHub - bitrise-step…

[Step] "bridge" an environment variable - assign the value of one Step's output to another Environment Variable

Feature Requests Released

eliot_pear June 21, 2017, 1:31am 2

@viktorbenei Do you think this feature request was covered by the addition of “step output aliases” in Monthly release of Bitrise CLI tools and summary of updates (May, 2017) - CLI v1.6.1 ?

1 Like

Topic		Replies	Views
Can't access "Environments to share" values in steps started by "Bitrise Start Build" step Question & Answer step	2	610	October 10, 2021
Sharing Env variables between stages Build Pipelines	9	1397	April 12, 2023
How to pass a custom env variable when triggering a Bitrise workflow? Question & Answer	10	5846	March 5, 2018
Export SOMEVAR does not set the environment variable for another Step Question & Answer	1	1753	July 18, 2017
Define environment variables for Bitrise Start Build step Released contrib-this-feature , released	8	1846	August 25, 2021

[Step] "bridge" an environment variable - assign the value of one Step's output to another Environment Variable

Related Topics