Maximum recommended number of configurations


Let's assume I want to have 1000 build configurations on one build server. How will TeamCity server handle such a load? I know, that generally answer depends on number of agents, frequency of build and many other parameters. But my question is how performance depends on number of build configurations? Is there the maximum recommended number of configurations, or, may be, maximum tested number? What is the maximum number of build configurations on one TeamCity server JetBrains have ever met?

1 comment
Comment actions Permalink

Hello Anton,

The server performance does not depend on number of build configurations significantly. Build configuration is just an xml file and big number of xml can slow down server UI. However it's also depend on server hardware.

You can find some examples of real server configurations in this article: Some customers reported that they have about 5000 build configurations.


Please sign in to leave a comment.