Max. no. of build configurations in TeamCity

Hi,


We  are using TeamCity Server of 7.1.3 version. Subversion as VCS and VCS Trigger as part of Build Trigger.
FYI - There are about 52 projects and 28600+ build configurations configured in TeamCity.


Ours is a typical scenario, where we have a requirement to configure each project with 550+ build configurations for every dev branch that was created. As the no. of dev branches gets created, the projects (with 550+ build configurations) for the same in teamcity are to be configured.
Problem is that as the no. of build configurations exceeds 28000+, builds are failing as it is not able to collect the changes from the svn. Till now, we were deleting the projects which are not in use for months so that the count of build configurations is decreased and then proceeding for "Build History Clean-up" to make the builds success. But now, the scenario has come where all the 52 projects in use (active) and the builds are failing on commit.


Here the question whether is there any configuration parameter, where we can specify the max. no. of build configurations in TeamCity.



Thanks and Regards,
Rajesh N

3 comments
Comment actions Permalink

Hi Rajesh,

There is no built-in limit on the build configuration number and the actual reason should be elsewhere.
Could you please post the full error you get? (temacity-vcs.log snippet would be great)

A probbaly cause is that TeamCity might generate too many requests for your Subversion server which then fails to respond properly to TeamCity requests when the flow of requests reach some limit.

0
Comment actions Permalink

Hi Yegor,


As per my observation, none of the logs are getting updated whenever there is a build issue occurred due to build configuration limit.
Build is failing even if only one build is triggered at that time. So, it might not be due to Subversion server response. Please let us know how can we proceed further.


Thanks and Regards,
Rajesh N

0
Comment actions Permalink

Rajesh,

As you might imagine we would need detailed description of the message you get and the inapporpriate behavior you see to look into the issue.
You have mentioned builds are failing. Could you attach relevant build logs?
Also full set of server logs covering the issue as well as server thread dumps might be good for a start.

0

Please sign in to leave a comment.