Currently, there is no support for environment variables at the pipeline or stage level. This limitation forces me to define variables within each workflow, which can become cumbersome, especially when they are needed across multiple workflows. Having environment variables available at the pipeline or stage level would streamline configuration and improve efficiency. Could you consider adding this feature in future updates?
Hi @hari-bytecronix 
, welcome to the Bitrise forum.
Can you share some use cases/examples of what you’d like to achieve? It will help us fully understand the pain point.
Thanks so much!
Hi @jeremyp ,
For example, we previously created two workflows: android_gen and ios_gen. The android_gen workflow is responsible for generating Android builds, while ios_gen handles iOS builds. In workflows we are consuming one environment variable to change app targeted environment details. We configured a pipeline to run both workflows in parallel to generate builds for the dev environment.
Now, suppose we want to create a pipeline for the QA environment. If the pipeline supports environment-level variables, we can reuse the existing workflows by simply creating a new pipeline that sets the environment variable to QA.
1 Like
Thanks for the extra context @sushant.bhatnagar, this is super-helpful 
This is a capability we are considering for the future, but is not yet scheduled on the roadmap. Your feedback here helps make the case for it, thank you 
Other Bitrise users: feel free to add your support for this feature here. Please try to include example use cases.