I am in a similar position where I am coming from Buddybuild and wishing to port over the same functionality into Bitrise.
My configuration in Buddybuild has a single app with three different schemes – dev, staging, and production – each scheme configured for their respective environments. Our unit tests are only run against the dev scheme. If the tests fail, the build needs to be marked as failed.
My approach is to have a commit trigger a “dev” workflow, which will run the tests and archive the app for ad-hoc deployment. Once the build completes and all tests pass, I would then trigger the “staging” and “production” workflows. “staging” will be archived for ad-hoc deployment as well, while “production” will be archived for app-store deployment. However I am running into some issues with this implementation:
bitrise-run step fails with the following error: “bitrise_config_path does not exist: ./bitrise.yml”. How should I reference the path to the config file of another workflow from the
- Am I able to trigger two workflows to run in parallel? It seems that I can only do them sequentially.