Searching all the community forum by keyword 'best practices' gave me some posts, but I haven't find anything I interested in. Some of that was outdated, some that wan't replied with details.
For example this post https://devnet.jetbrains.com/message/5493106#5493106 has a quite serious questions from Ryan which were not answered. I am interested in answers too. So, questions:
What is the best practice for building a project under multiple configurations(debug, release, etc., not TeamCity build configurations) and platforms? Should each be a separate project, is there some easy way to handle this via build parameters, or is it considered standard to just lump them all under one configuration as separate build steps?
I am requesting the best practices for enterprise-level TeamCity using. I mean how to organise thousands of build configurations multiple OS and architectures, hundreds of projects, gigabytes of artifacts, tens of agents?
Let me try to cover more aspects in enterprise TeamCity deployment with asking more questions. How to manage all that configs and have the fast and reliable system at the same time? What is estimate resource consumpsion? Have you ever test your TeamCities under high loading?
So compiling the above:
How to organise the projects/configs
How to organaise resources for them
And keep the system run builds fast, respond fast and reliably?
If I missed something you think is important please add it to this thread.