Some reasons why app cloning would work currently where separate workflows within a single app do not:
- PR trigger settings conflict with scheduled builds. E.g. if a PR merge to
master happens while a scheduled build is running, then the running scheduled
master build is aborted
- display a badge for specific scheduled workflows (not branch). E.g. so I can have a table on my GitHub README page that shows a cross-table of build type (alpha, beta, prod) vs device type (iPhone 8, iPhone X, iPhone SE, iPad Air, …). Right now I need a separate app for each of these because the badge only provides for the git branch name (all devices use
- various mono-repo situations. E.g. we currently have 1 repo that builds 4 iOS apps. So we have 4 apps minimum (which is unfortunate, because they all have the same settings except for one value)
Yes, each of these situations could be addressed some other way. E.g. segregating scheduled builds from PRs would be nice. And making badges more granular would be good. But for now, cloning is the least-worst solution. (I’m glad to having something that works, but maintaining them all is quite a task when one little thing needs to be changed!)
Yes, having a command line tool where we could pass in a bitrise.yml to configure every aspect would be great (including app name, app settings), as well as the workflow details.
Hope this helps!