# Multiple builds for one repo

**URL:** <https://discuss.circleci.com/t/multiple-builds-for-one-repo/662>\
**Category:** Build Environment\
**Created:** [November 20, 2015, 12:31am UTC](https://discuss.circleci.com/t/multiple-builds-for-one-repo/662 "2015-11-20T00:31:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\
**Post date:** [November 20, 2015, 12:12pm UTC](https://discuss.circleci.com/t/multiple-builds-for-one-repo/662/3 "2015-11-20T12:12:30Z")

</div>

What exactly would your workflow look like? Would you like to be able to trigger the one _or_ the other build? Or it is fine for you to run both the iOS and the OS X build every time?

If it is fine to run them both, just putting the two build commands in the `dependencies` and `test` section should be enough:

```auto
dependencies:
  override:
    - ./deps-osx.sh
    - ./deps-ios.sh

test:
  override:
    - ./build-test-osx.sh
    - ./build-test-ios.sh

```

(The script names are completely random for demonstration purposes.)

If you would need to run only certain parts of the build, [this API endpoint](https://circleci.com/docs/1.0/parameterized-builds/) allows you to trigger a new build with a certain value set for an environment variable, which you could subsequently base the decision of build commands on:

```auto
test:
  override:
    - if [[! -z $CIRCLE_OSX_BUILD]] ; then ./build-test-osx.sh ; fi
    - if [[! -z $CIRCLE_IOS_BUILD]] ; then ./build-test-ios.sh ; fi

```

Another option would be to have two separate projects, one for iOS and one for OS X, one of which would contain all the code and the other one would only contain a _circle.yml_ file. This config-only build would then pull in the project code during the build with `git pull`.

Would any of those options work for you?

---

_[View the full topic](https://discuss.circleci.com/t/multiple-builds-for-one-repo/662)._