We're looking at using Versioned Settings for our repositories, to allow hotfix branches to build using older build definitions. After trialling, we want to re-enable UI editing. Unfortunately, we use branch protections on the master branch, and we're not keen on giving the TC user admin rights on the repo to get around branch protections.
If I have the following config:
Repo A: Contains only .teamcity - TC versioned settings is configured to save to this repo
Repo B: Contains a submodule mapped to .teamcity that points at Repo A
What will TeamCity do when running a build where the submodules current commit is older than the most recent commit in Repo A? Will it happily accept the .teamcity folder in Repo B? or will it not see it and revert to its most recent config?