# Some guidance for parallel builds

**URL:** <https://discuss.bitrise.io/t/some-guidance-for-parallel-builds/12470>\
**Category:** Question & Answer\
**Tags:** react-native\
**Created:** [March 31, 2020, 4:39am UTC](https://discuss.bitrise.io/t/some-guidance-for-parallel-builds/12470 "2020-03-31T04:39:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![luciano.lima](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/luciano.lima/32/2937_2.png) [@luciano.lima](https://discuss.bitrise.io/u/luciano.lima)\
**Post date:** [March 31, 2020, 4:39am UTC](https://discuss.bitrise.io/t/some-guidance-for-parallel-builds/12470/1 "2020-03-31T04:39:52Z")

</div>

I have some workflows:

- `pre-build` for ssh, git clone, cache:pull, yarn install
- `tests` for typescript check, jest tests and sonarqube scanner
- `android` and `ios` for native build with fastlane
- `android-devices-test` and `ios-devices-test` to send to AWS DeviceFarm

Start this year, we migrate to a team account with parallel build. Before this, we run one workflow after another and inside the `android` and `ios` workflows (including devices-test) I add a version bump step with fastlane and push to repo.

When I push some code, both workflows are triggered and the last one aways fails because the first one do a version bump and push these changes. So the last one fails because needs a pull before.

My question, I can do a pull before a push, but is there another way to maintain parallel build and one doesn’t affect other?  
I try to run one and call other after finish but this give 82min builds. It’s so long.  
What is the better way to do this? Pull code before do the version bump?

Thanks!

---

<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:** [April 6, 2020, 9:49am UTC](https://discuss.bitrise.io/t/some-guidance-for-parallel-builds/12470/2 "2020-04-06T09:49:55Z")

</div>

Hi @luciano.lima!

The approach we recommend to incrementing version numbers are one where you do this within the virtual machine, so you don’t have to commit the numbers and can avoid this conflict. Please see: [https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/](https://devcenter.bitrise.io/builds/build-numbering-and-app-versioning/)

---

<div class="post-metadata">

**Author:** ![luciano.lima](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/luciano.lima/32/2937_2.png) [@luciano.lima](https://discuss.bitrise.io/u/luciano.lima)\
**Post date:** [April 7, 2020, 8:46pm UTC](https://discuss.bitrise.io/t/some-guidance-for-parallel-builds/12470/3 "2020-04-07T20:46:48Z")

</div>

This help with parallel builds?  
This will greatly increase the number of the build because we have workflows that run on each push. We prefer the build to increase with each release to the store.

---

<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:** [May 7, 2020, 8:51pm UTC](https://discuss.bitrise.io/t/some-guidance-for-parallel-builds/12470/4 "2020-05-07T20:51:45Z")

</div>

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