User guide

21
5. Specify how the component gets the files used during the deployment by selecting one of the following 3
options:
i. Builds with application: When ‘Builds with application’ is selected, the component is integrated
with Team Build and inherits the Team Project and Build Definition from the release template. At
release time, those fields will be used to provide a selection of builds from which a specific
package to release will be selected.
ii. Builds independently: When ‘Builds independently’ is selected, the Team Project and Build
Definition need to be provided. At release time, those fields will be used to provide a selection of
builds from which a specific package to release will be selected.
iii. Builds externally: When ‘Build externally’ is selected, a path needs to be supplied to get the base
package location. At release time, a subfolder (corresponding to a package version) will need to be
entered so that the full package location path can be derived.
6. Go to the Deployment tab. This tab allows you to configure how your component will be installed at the
time of deployment on the target server.
What are Tools?
A Tool assists in the execution of various deployment scenarios that are often encountered.
Tools come in the form of a batch file (.bat or .cmd), a PowerShell script (.ps1), an executable
(.exe), etc.
7. Select a tool from the Tool dropdown. The Command and Argument fields will automatically be updated
with values configured in the selected tool.
If you decide to use a custom tool, you will need to manually enter the installation command and its
argument in the Command and Argument fields. You must also make sure that any files referenced by
your command will be available in your package location at the time of deployment.
8. Go to the Configuration Variables tab. This tab shows the list of configuration variables used by the
component.