You normally only create a few build definitions, and the GUI is the
best place to create them. Why would you want/need to create a build
definition programatically?

Cheers,
Geoff

On 9/8/2011 12:53 PM, adefarlo wrote:

I see this site has good documentation on requesting a build via the
api. However, can someone point me to documentation on also creating
a build definition via the api. The issue is this, we need to pass
two parameters to the build. This is normally done via the arguments
section of the build definition, so the thought is that we should
programatically first create the build definition with those
parameters, then programatically request a build.

For us, a build is not a source code build but building a product in our core claims processing system. We are using the RTC build function to kick off a custom app which builds a product in the claims system. We need to pass a parameters to that program which indicate the product id to build and the target environment to build it in....

You normally only create a few build definitions, and the GUI is the
best place to create them. Why would you want/need to create a build
definition programatically?

Cheers,
Geoff

On 9/8/2011 12:53 PM, adefarlo wrote:

I see this site has good documentation on requesting a build via the
api. However, can someone point me to documentation on also creating
a build definition via the api. The issue is this, we need to pass
two parameters to the build. This is normally done via the arguments
section of the build definition, so the thought is that we should
programatically first create the build definition with those
parameters, then programatically request a build.

My comment should apply whether you are building source code or are
building a product in a claims processing system. You don't want to
generate a new build definition for every variant ... you normally want
to abstract that variance in build properties. In particular, you'd
normally want the parameters that indicate the product id and the target
environment to be build properties, rather than creating a separate
build definition for every product-id/target-environment combination.

Cheers,
Geoff

On 9/8/2011 5:08 PM, adefarlo wrote:

For us, a build is not a source code build but building a product in
our core claims processing system. We are using the RTC build
function to kick off a custom app which builds a product in the
claims system. We need to pass a parameters to that program which
indicate the product id to build and the target environment to build
it in....

gmclemmwrote:
You normally only create a few build definitions, and the GUI is the

best place to create them. Why would you want/need to create a
build
definition programatically?

Cheers,
Geoff

On 9/8/2011 12:53 PM, adefarlo wrote:
I see this site has good documentation on requesting a build via
the
api. However, can someone point me to documentation on also
creating
a build definition via the api. The issue is this, we need to pass
two parameters to the build. This is normally done via the
arguments
section of the build definition, so the thought is that we should
programatically first create the build definition with those
parameters, then programatically request a build.

You should not need to create a new build definition each time. You can override the value of build properties when requesting a build. The API to use for requesting a build is ITeamBuildRequestClient.requestTeamBuild.

Thanks! It was not clear to me that the properties could be passed in the request. I thought they had to be set in the definition...