Continuous Delivery with psake and TeamCity - Visualizing a pipeline REVISED

The series so far:

1. Creating a Local Build With psake, Part 1: Compiling
2. Creating a Local Build with psake, Part 2: Testing
3. Continuous Delivery with psake and TeamCity - Reusing the Local Build to Create a CI Build
4. Continuous Delivery with psake and TeamCity - Preparing for a pipeline
5. Continuous Delivery with psake and TeamCity - Creating a pipeline with artifact dependencies
6. Continuous Delivery with psake and TeamCity - Visualizing a pipeline
7. Continuous Delivery with psake and TeamCity - Environment Configuration Management
8. Continuous Delivery with psake and TeamCity - Time for Some Refactoring
9. Continuous Delivery with psake and TeamCity - Config Templates

In one of my pervious post, Continuous Delivery with psake and TeamCity - Visualizing a pipeline I wrote about how you could sync build numbers between build configuration. In that post I suggested to create a file that contained the build number which would be published to the artifact repository in TeamCity and used by dependent build configurations to set the build number. That was not exactly an optimal solution.
In Continuous Delivery with psake and TeamCity - Time for Some Refactoring I talked about how you could use the inherited build number from the “parent” build configuration and pass that into the build script and then set the build number in TeamCity. This was certainly a better solution, but it would be better to just let TeamCity handle setting the build number. To fix this, go to General Settings in the dependent build configuration and put dep.btX.build.number in the “Build number format” text box.

Actually I have been doing it this way for a long time now, so I should have written this post much sooner. Sorry.