One of our installations contains many pieces - website, web services, background apps, windows services, queuing mechanisms, desktop GUI apps, etc. Written in a number of different languages, and built as separate projects.
There are, of course, dependencies among them. Most work against a common database, and have a dependency on the table schema. The older VB desktop GUI apps (which we've not yet been able to eliminate) depend upon a COM object, written in C++.
I've been reading through your whitepapers, and everything seems simple and clear, there. Mainly because the examples are simple and clear.
How do you deal with more complex situations?
Does a build wrap a single project? Or can it wrap multiples? How does Buildmaster deal with dependencies between projects?
Does a release map to a single projects? Or can it contain multiples?
Would a complex environment of the sort I've described be organized as a single release? Or would the various parts be handled as separate releases?
Is there any mechanism for meta-releases? For a top-level release that contains multiple lower-level releases?