Trigger build on non-default branch that has revision in default branch.

Per your documentation: “If the default branch is one of the branches in the merging/fast-forwarding, the changes are always calculated against the default branch, if there is a build on same revision in the default branch, TeamCity will not run a new build on the same revision.”

My organization requires our default branch be develop and the main branch be fast forwarded using develop. Each branch must build a separate deployment asset. Is it not possible to overcome the behavior described above with a trigger, and to build main every time there is a fast forward?