Teamcity 10 offers new feature storing project settings in version control
What is the best practice to follow in terms of storing these settings?
- Keep it in the same repo where code resides?
- Put it into separate repo?
Teamcity 10 offers new feature storing project settings in version control
What is the best practice to follow in terms of storing these settings?
Copyright © 2021 Jogjafile Inc.
We have put it into separate Git repository called teamcity-settings after having it in repository with some other stuff for continuous integration. The problem with having it together with something else was that it makes too much "noise" in git history, since every TeamCity build configuration update is doing a commit.
So my suggestion - let TeamCity settings live it's own life in version control. :)