multile definitions in deploymentConfiguration file

nirali

deplymentConfiguration file can have more than one definition
If we have more than one definition in deploymentConfiguration file, still we can use only one of them in the deployment section at a time.
Then whats the use of other definitions ? Does the deployment need to be changed every time, I want to use different definition ?
Or is there some script required to make selection of definition dynamically ?

Thanks

Adam Stoller

deplymentConfiguration file can have more than one definition If we have more than one definition in deploymentConfiguration file, still we can use only one of them in the deployment section at a time. Then whats the use of other definitions ? Does the deployment need to be changed every time, I want to use different definition ? Or is there some script required to make selection of definition dynamically ? Thanks

You can have multiple definitions within a single deployment configuration file to do multiple things during a single deployment - usually. If you want to have multiple definitions and call only one of them each time you use that configuration file, you would have to pass the name of the definition in as a parameter on the command line and use that variable within the execDeploymentTask. This isn't the recommended usage though.

If you want to call this deployment or that deployment - it's better to have distinct configuration files

csv.zip