We are currently running TeamCity 1.2 for our changeset, and nightly builds. We had previously used cruisecontrol but it had significant stability issues. We really like the integration with Intellij that TeamCity provides.
For our current project we inherited a fairly large, older java system that did not have very strict coding standards or quality checks. We have a pretty severe inspection configuration we run on our newer code. We want to maintain that high level of inspection checking on new code and changes made to this project. Unfortunately we are running into some very serious performance issues doing this. Our current inspection build takes just under four hours! This does not include the hour it takes to render the inspection report.
I was hoping there were some configuration changes we could make to reduce the length of this build. Here are some questions:
1. It currently appears that there is no way to run inspections on new code only. Is this the case?
2. I would like to exclude our test directory from being inspected. This directory includes unit tests, fixtures and supporting code, that is not part of the deployed system. In Intellij I have the option of unchecking "Include test sources" from an inspection. I can not seem to find an equivalent option in TeamCity. Is this possible?
3. Are there known inspections that are very time intensive? Perhaps there is a subset of inspections I could disable to give us a significant performance boost.
I appreciate the assistance in advance. We find a lot of value in TeamCity but the performance issues here are getting overwhelming.
John Deere Agri Sevices