This seems like a silly question, but I have trolled this list and the FAQs and TeamCity doc and am either just missing it or not getting it....
So, we have a relatively large project and I would like to create the following build configurations:
1. source build
2. unit test execution
3. code coverage
4. code inspections
What I have done to date is to create the source build configuration, copy that and insert the property Unit Test patterns. Then I copied the Unit Test configuration and flipped on the code coverage checkbox. Then I copied the source build and changed the build runner to Code Inspections.
But there has to be a better way. The problem is that if I make a change to the source build configuration I have to run around doing that in all the configurations. It seems like I should be using dependencies -- artifact dependencies? -- to accomplish what I am trying to do here. i.e. the unit test execution build forces the source build to run and then executes the unit tests. The code coverage forces the unit test build which forces... etc. However, it is not at all clear to me how you would set up a 'unit test execution' configuration using artifacts. For example, in that case I don't want/need the code to be re-pulled and bulit. So, do I select "Do not checkout" and put a build dependency on the source build configuration? Is that the intent?
Why have these build configurations? Well, the project is large enough and we have enough tests, etc. where I don't (for example) want to run all the code coverage on every check-in. That is something to schedule for each night. Same with the code inspections. We only want to trend that information nightly.
Pretty sure the way I have set it up is not the best practice. Any pointers to documentation, examples or replies appreciated.