# Define environment variables for Bitrise Start Build step

**URL:** <https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273>\
**Category:** Released\
**Tags:** contrib-this-feature, released\
**Created:** [June 4, 2018, 6:53am UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273 "2018-06-04T06:53:13Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![asos-petergoldsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/asos-petergoldsmith/32/1154_2.png) [@asos-petergoldsmith](https://discuss.bitrise.io/u/asos-petergoldsmith)\
**Post date:** [June 4, 2018, 6:53am UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/1 "2018-06-04T06:53:13Z")

</div>

For the Bitrise Start Build step, there doesn’t appear to be a way to pass through environment variables, is this correct?

I can see this can be done with the Build Trigger API [Redirecting…](https://devcenter.bitrise.io/api/build-trigger), however I don’t know if we can use that in conjunction with the Bitrise Wait for Build step?

**Use case:**  
We’re splitting some work across concurrent builds, and to define what each ‘child’ build should do, and where to place its artefacts, we need to be able to pass context from the parent. The parent then needs to be aware of the completion success/failure of all the children to consolidate artefacts and overall success/failure.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [June 6, 2018, 4:29pm UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/2 "2018-06-06T16:29:00Z")

</div>

Awesome idea @asos-petergoldsmith! Did you want to create this as a #feature-request? Should I move it there?

---

<div class="post-metadata">

**Author:** ![asos-petergoldsmith](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/asos-petergoldsmith/32/1154_2.png) [@asos-petergoldsmith](https://discuss.bitrise.io/u/asos-petergoldsmith)\
**Post date:** [June 6, 2018, 5:34pm UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/3 "2018-06-06T17:34:32Z")

</div>

Yup, it certainly is a feature request then if it isn’t currently possible.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [June 7, 2018, 7:59am UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/4 "2018-06-07T07:59:07Z")

</div>

Got it! Moved it into #feature-request - feel free to vote on it here 😉

I’ll also ping the tooling team with this, see if they can add it to their sprint or something - or feel free to send a PR into the step, all of our steps are open source! 😉

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [July 7, 2018, 8:08am UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/5 "2018-07-07T08:08:31Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![BirmacherAkos](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/birmacherakos/32/1319_2.png) [@BirmacherAkos](https://discuss.bitrise.io/u/BirmacherAkos)\
**Post date:** [September 12, 2018, 3:07pm UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/6 "2018-09-12T15:07:10Z")

</div>

Hi @asos-petergoldsmith !

We have released a new version [(0.11.1)](https://github.com/bitrise-steplib/bitrise-step-build-router-start/releases/tag/0.11.0) of the “Bitrise Start Build” step.  
It will be available today.

With the new version, you can share envs between the triggered workflows.

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [October 15, 2018, 2:13pm UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/7 "2018-10-15T14:13:45Z")

</div>



---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [October 15, 2018, 2:14pm UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/8 "2018-10-15T14:14:34Z")

</div>

I re-opened this thread as it seems the auto-close did carry with it from the #question-answer category and was actually closed automatically by the system… Sorry for the inconvenience @asos-petergoldsmith

---

<div class="post-metadata">

**Author:** ![bitce](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/bitce/32/1639_2.png) [@bitce](https://discuss.bitrise.io/u/bitce)\
**Post date:** [August 25, 2021, 11:31am UTC](https://discuss.bitrise.io/t/define-environment-variables-for-bitrise-start-build-step/5273/9 "2021-08-25T11:31:31Z")

</div>


