Jazz builds chicken-n-egg question

I recall talking with another individual who was doing some work integrating with the build system and this question came up. Perhaps adding the ability to 'push' this bootstrap file to initiate the product's build to the build machine is reasonable.

Previous to M3, you needed to have a bootstrap build file that would fetch
the code before invoking your "real" build file.

In M3, we've added support to the engine so you can specify the workspace in
the build definition, and it will be fetched for you, to the destination you
specify, prior to invoking your primary build file.

Details in the new and noteworthy and updated getting started docs when M3
is released, near Oct 8th.


"harryk" <harry@rocketgang-dot-com.no-spam.invalid> wrote in message
news:fdogfd$63i$1@localhost.localdomain...

From my understanding, a build definition specifies a hardcoded path
on the build machine to a build.xml file. In many systems, that
build.xml file is in CM with all the other project artifacts and
would load on a teamFetch. So, how did the build.xml get on the
build machine in the first place to do the teamFetch?

Is the best practice to have a proxy build.xml file on the build
machine that simply does a teamFetch and then launch the project's
real build.xml file? Any other best practices, or am I confused
about the build definition?

Many thanks.