Since you’re working with changes triggered by another system, it does seem like setting additional build hooks would be the way to go here.
In many (perhaps most) other cases, where the changes are made in Git rather than a remote API, a rebase between branches would be required before a re-deploy would be useful. (And pushing the rebased commits would trigger the new branch deploy anyway.)
Perhaps a feature that would make more sense for this particular use case would be the ability to set multiple branches to build from a single build hook. I could see this serving use cases outside of Split Testing, as well.
Any updates on this feature request? Or maybe a link where I can track progress of this feature request?
This is a feature we are really looking forward to use in our project. This is because we have allot of different people who can update the site and trigger a build (content updates in DatoCMS). And since a few weeks we are using the split testing feature. And now we have to remind everyone to build all the different variants which are used by the split tests when updating the website. A feature which could automate this would help us allot!