Another Dimension, Target

[mpotter@…]

Suggestion (I don't currently need this, but I can see someone else might).

Currently Builds are organized in two dimensions:

• Build Configurations (e.g. bitten-trac-0.10, trunk)
• Platforms: (e.g. Unix, Windows)

In some cases there may be another dimension, for now I will call it 'Target'.

In my case, we have a repository from which multiple applications are built from; there are large pieces of common code between most of these applications. (e.g. ClientA, ClientB, Server1, Server2, Server3). In the past I have experimented with:

• Having a Build Configuration build all of the targets.
• Having multiple Build Configurations, one each for each of each of the targets; but then permuted over the trunk and each active branch.
• Having a Build Configuration for the trunk and each active branch, then overloading the Platform for each Target.

We are currently using the last option. Since we currently only have one platform this is not an issue. However this might change for us, and I could see could be different for some other installation.