Does "Load Additional Settings From a VCS" obsolete "versionedSettings.modifyDependencies"?
In a previous post (https://teamcity-support.jetbrains.com/hc/en-us/community/posts/360009990599-2020-Roadmap-Per-branch-configurations-when-) I asked about “per branch build configurations” and was directed to use the experimental setting teamcity.internal.versionedSettings.modifyDependencies.
Now in TeamCity 2023.11 I see the new feature Versioned Settings: Load Additional Settings From a VCS (https://www.jetbrains.com/help/teamcity/2023.11/what-s-new-in-teamcity.html#Versioned+Settings%3A+Load+Additional+Settings+From+a+VCS).
This new feature and the internal experimental setting sound the same. Is that true? Does the new “load additional settings from VCS” setting obsolete the experimental setting? I only need to be able to add new build configurations in my master branch with old branches continuing to use the old build configurations and snapshot dependencies.
If this new feature does not obsolete the experimental setting, does the experimental setting still work? I want to upgrade to 2023.11 but need some confidence in the upgrade path.
Please sign in to leave a comment.
Experimentally the answer appears to be “yes”. We tested this in our dev server after upgrading to 2023.11 and teamcity.internal.versionedSettings.modifyDependencies no longer did anything but the "Load Additional Settings From a VCS" setting seemed to do what we wanted it to.