Share Pipeline variables

Share environment variables between Pipeline Stages.

Description

Share environment variables between Pipeline Stages.

Variables shared by the Step will be available in subsequent stages workflow's as one-off env vars as if provided manually on the website.

🧩 Get started

Add this step directly to your workflow in the Bitrise Workflow Editor.

You can also run this step directly with Bitrise CLI.

Example

steps:
- script@1:
    title: Should we run UI tests?
    inputs:
    - content: |-
        set -eo pipefail
        # Custom logic goes here
        envman add --key RUN_UI_TESTS --value true
- share-pipeline-variable@1:
    title: Configure next pipeline stage
    inputs:
    - variables: |-
        RUN_UI_TESTS
        BUILD_TYPE=debug

⚙️ Configuration

Inputs

Key	Description	Flags	Default
variables	A newline (\n) separated list of variable names or NEW_ENV=NEW_VALUE for declaring new variables. The input uses a KEY=VALUE syntax for declaring new variables. The first = is the delimiter between the key and value of the environment variable. A shorthand syntax of ENV_KEY can be used for ENV_KEY=$ENV_KEY when sharing an existing environment variable (ENV_KEY). Examples: MY_ENV_VAR=my value EXISTING_ENV_VAR	required
app_url	The app's URL on Bitrise.io.	required	$BITRISE_APP_URL
build_slug	The build's slug on Bitrise.io.	required	$BITRISE_BUILD_SLUG
build_api_token	API Token for the build on Bitrise.io.	required, sensitive	$BITRISE_BUILD_API_TOKEN

Outputs

There are no outputs defined in this step

🙋 Contributing

We welcome pull requests and issues against this repository.

For pull requests, work on your changes in a forked repository and use the Bitrise CLI to run step tests locally.

Learn more about developing steps:

• Create your own step
• Testing your Step