I have a very basic configuration:
1) Compile Java
Even though this seems like a pretty vanilla configuration, it's not clear to me how I should configure the dependencies for this project. I assumed the "compile" would do the label, get, and build, of the code. Then, each of the subsequent items would just depend on the output of that first step. If that's true, then is this achieved by simply making all the downstream build configuration dependent on this first item? And, does that mean each of these dependent items will use the results of the get that was done in the first step? Or, will each of these do it's own get from the VCS repository?
Also, if they each do their own get and I tell the compile configuration to do a custom build against and older label, how will those downstream configuration know that they are also supposed to do their get using this older label? For example, if I tell the compile configuration to use the old "1.1" label, while the CheckStyle build configuration examine the source from this older label or will use the source that was retrieved using the old "1.1" label.
Overall, it would just be nice to understand how and when TeamCity does its get from VCS, how and when it labels (before or after the build), and how custom build againt old labels factor into this? I'm sure it's all very simple, but there's nothing I find in the docs that seems to explain this general policy.
Also, your live demo has an example that's already out there that seems like it would serve as a great reference for what I'm trying to do. It includes most of the same configurations I am using. Is there any way you can provide the Ant scripts and underlying build configuration files for that example? That would be a tremendous help. Right now, while the documentation for the product is very good, it tries so hard to generalize that it avoids providing any good contextual examples that would at least cover some of the common scenarios.