Hello!
I’m looking at establishing some auto-submit workflows for our team. We want the majority of our devs to run pre-flight builds through Horde before submitting. Horde auto-submit seems to be a great way to make the pre-flight process more “fire-and-forget”, such that devs don’t need to intervene after pre-flight passes.
When testing, I found that Horde will not submit changes if the preflight changelist still contains checked out files. However, the Submit Tool does not revert checked out files, nor does it move the checked out files to a new changelist after shelving. To work around this, Submit Tool users need to move their checked out files manually if they want Horde auto-submit to work.
While we could modify Horde or the Submit Tool to work around this, I’d like to know more about how Epic recommends developers to use Horde auto-submit, especially with Submit Tool.
Does Epic have a recommended workflow for utilizing Horde Auto-submit with the Submit Tool? How should devs be preparing their changelists before running a pre-flight job with auto-submit checked? Are devs expected to do anything else in their Perforce workspace after their shelf is auto-submitted by Horde (such as reverting out-of-date files)?
Thanks!
- Sam