Team Build Properties

Edit online

The following sections describe how to define the Team Build properties used in a build definition. Each section describes a set of Team Build properties that can be defined using the teamBuildProperty element. The teamBuildProperty element accepts two attributes, name and value, which are both required. Other build properties can be referenced when specifying a value using the ${propertyName} format.

Code as many teamBuildProperty elements as are needed to define the Team Build properties for the build definition. One teamBuildProperty element is needed for each Team Build property. Code the teamBuildProperty element within the createBuildDefinition or updateBuildDefinition element. Specify only those Team Build properties that are valid for the type of build you are defining. The teamBuildProperty element is not required and may not be applicable to the type of definition you are creating. Refer to Build Reference to determine if teamBuildProperty elements are valid for the build you are defining.

All Team Build properties support the standard property attributes, but most attributes are ignored as the values for the attributes are set internally and can not be overriden. The following table describes the attributes and what affect, if any, specifying the attributes has on the build property itself.

Attribute Required Description

name

Yes

 Name of the build property. Valid names are described in each of the following sections.
 

Yes
Value of the build property. Valid values and restrictions are described in each of the following sections. Restrictions on the valid values are noted in the value column. The restrictions noted are as follows:
Restriction Description
boolean This is a boolean value which must be specified as either true or false.
integer This must be an integer value.
true/false This is a boolean value which must be specified as either true or false.
value list One of the listed values must be specified. For example: ALWAYS, NO_ERRORS, or NO_WARNINGS.

asis

No

 Valid values are true and false. The default is false. Specifying this attribute will control how the property is resolved.

description

No

This attribute is ignored.

genericEditAllowed

No

This attribute is ignored.

kind

No

This attribute is ignored.

label

No

This attribute is ignored.

override

No

 Valid values are true and false. The default is false. Specify true for this attribute when updating restricted Team Build property values.

required

No

 This attribute is ignored.

scheduleOverride

No

 This attribute is ignored.

wellKnown

No

 This attribute is ignored.

teamBuildProperty Element - Ant with Enterprise Extensions Build

The following table describes the valid values for teamBuildProperty element attributes for an Ant with Enterprise Extensions build:

name value Description

teamz.build.ant.bpxwdyn.options

  

BPXWDYN Options: Dynamic allocation options. Define any options that you want to pass to the BPXWDYN interface. The default value is MSG(1), which means that messages are directed to file descriptor 1, which is the build log file for all Ant with Enterprise Extensions and dependency builds.

teamz.build.ant.reuseISPFSession

true

false

 Reuse ISPF Session: Specify true if you have translators that use a call method of ISPF command or EXEC and wish to avoid the overhead of repeated session setup and teardown. Note: This option is for advanced use cases only.

teamBuildProperty Element - z/OS Deployment Build

The following table describes the valid values for teamBuildProperty element attributes for a z/OS® Deployment build:

name value Description

team.deploy.common.action

""

deployMain

loadMain

rollbackMain
Deploy type: Specify the type of deployment to perform. Valid values are:
Value Description
"" Load and deploy (a blank or empty value).
deployMain Deploy.
loadMain Load.
rollbackMain Rollback.
This property should be included as a Schedule Team Property.

team.deploy.common.deploy.postCommand

  

Deploy post-command: Command to be executed after deployment.

team.deploy.common.deploy.preCommand

  

Deploy pre-command: Command to be executed prior to deployment.

team.deploy.common.load.ftp.hostname

   Host name: FTP host name.

team.deploy.common.load.ftp.passwordFile

   Password file: FTP password file.

team.deploy.common.load.ftp.userid

  

User ID: FTP user ID.

team.deploy.common.load.postCommand

   Load post-command: Command to be executed after load.

team.deploy.common.load.preCommand

  

Load pre-command: Command to be executed prior to load.

team.deploy.common.loadMethod

Copy

ftp
Load method: Specify the type of load method to use and the appropriate command and/or FTP properties. When Copy is specified, the FTP host name, user ID, and password file attributes must not be specified. When ftp is specified, the FTP host name, user ID, and password file attributes are required. Valid values are:
Value Description
Copy Copy data sets on this system.
ftp FTP data sets from another system.

team.deploy.common.localPackageRoot.dir

  

Deployed package root directory:* Local package root directory.

Note: It is advised to avoid using blanks or $ in the path as these characters (or their national language equivalents) can cause inconsistent results.

team.deploy.common.packageLabel

   Package: Specify the label of the target packaging build result. This property should be included as a Schedule Team Property.

team.deploy.common.packagedefinitionUUID

  

Package definition:* Specify the ID of the packaging build definition.

team.deploy.common.publishCumulativeDeploy

true

false

 Publish cumulative deploy manifest: Specify true to publish the cumulative deployment manifest file in the deployment result.
team.deploy.common.publishDeltaDeploy

true

false

 Publish delta deploy manifest: Specify true to publish the delta deployment manifest file in the deployment result.

team.deploy.common.publishRollbackManifest

true

false

 Publish rollback manifest: Specify true to publish the rollback manifest file in the deployment result.

team.deploy.common.remotePackageRoot.dir

  

Original package root directory:* Remote package root directory.

team.deploy.common.restoreMappingList

  
From Data Set/To Data Set: Specify the names of the PDS's created by the packaging build, and where to deploy them, in the restore mapping table. Specify a semicolon separated list of From/To paired dataset names. For example:
FROM0.DATA.SET;TO0.DATA.SET;FROM1.DATA.SET;TO1.DATA.SET

team.deploy.common.rollback.maximumKeep

integer

Maximum number of rollbacks to keep: Specify an integer value for the number of rollbacks to keep.

team.deploy.common.rollback.multipleAllowed

true

false

 Allow multiple rollbacks: Specify true to allow your team to roll back a saved package that was successfully deployed. The default is false. Note: Ignored for agents older than 5.0.1.

team.deploy.common.rollback.postCommand

  

Rollback post-command: Command to be executed after roll back.

team.deploy.common.rollback.preCommand

   Rollback pre-command: Command to be executed prior to roll back.
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.deploy.common.definition.version
    • team.deploy.common.filesystem
    • team.deploy.common.load.cd.deployment.useBuildAgentSettings
    • team.deploy.common.load.cd.localIp
    • team.deploy.common.load.cd.localPassword
    • team.deploy.common.load.cd.localPort
    • team.deploy.common.load.cd.localUserId
    • team.deploy.common.load.cd.nodeName
    • team.deploy.common.load.cd.packaging.useBuildAgentSettings
    • team.deploy.common.load.cd.remotePassword
    • team.deploy.common.load.cd.remoteUserId
    • team.deploy.common.openSummaryWorkItem
    • team.deploy.common.restoreMappingPath
    • team.deploy.ibmi.intermediateSaveFileLibrary
    • team.deploy.ibmi.pfRestoreMethod
    • team.deploy.ibmi.pfRestoreUsrCmd
    • team.deploy.ibmi.savePfForRollback
    • team.deploy.luw.runtimeRoot.dir
  • The following is a list of reserved properties names which can not be specified:
    • team.deploy.common.applicationDescription
    • team.deploy.common.applicationName
    • team.deploy.common.isCompletePackage
    • team.deploy.common.version
    • team.deploy.zos.script
    • team.enterprise.ibmi.ASPName
    • team.enterprise.ibmi.setASP

teamBuildProperty - z/OS Dependency Build

The following table describes the valid values for teamBuildProperty element attributes for a z/OS Dependency Build:

name value Description

team.enterprise.build.ant.alwaysRunPostBuildFile

true

false

 Always run post-build script: Specify true to run the specified post-build ant script whether or not the build was successful. The default is false, the specified post-build ant script will only be run if the build was successful.

team.enterprise.build.ant.bpxwdyn.options

  

BPXWDYN Options: Dynamic allocation options. Define any options that you want to pass to the BPXWDYN interface. The default value is MSG(1), which means that messages are directed to file descriptor 1, which is the build log file for all Ant with Enterprise Extensions and dependency builds.

team.enterprise.build.ant.buildChangesOnly

true

false

 Build changed items only: Specify true to build only the items that have changed since the last successful build. Specify false to build all items found in the workspace. The default is true.

team.enterprise.build.ant.buildableSubset

  

Build subset: Specify the name of an existing build subset. Build subsets specify a group of buildable items that will be included when executing a dependency build.

team.enterprise.build.ant.fullMinimumLoad

true

false

 Perform full minimum load: Specify true to load all items that recently changed or that depend on items that changed since the last successful build. This option is only valid for personal builds. Items will be loaded from the workspace specified on the build request to the resource prefix specified on the build request.

team.enterprise.build.ant.mandatorySubset

  

Mandatory Subset: If there are files to be included in each build for this build definition, specify the name of the subset containing the files that are required to be included in this build. The files in the mandatory subset are always built, even if they are not changed.

team.enterprise.build.ant.mandatorySubset.useInPersonal

true

false

 Include this mandatory subset in personal builds by default: Specify true to include the mandatory subset in personal builds.

team.enterprise.build.ant.postBuildFile

  

Post-build script: Specify the path to the post-build script on the build machine. This can be an absolute path on the build machine or may be a path relative to the current directory of the build engine process.

team.enterprise.build.ant.preBuildFile

  

Pre-build script: Specify the path to the pre-build script on the build machine. This can be an absolute path on the build machine or may be a path relative to the current directory of the build engine process.

team.enterprise.build.ant.reuseISPFSession

true

false

 Reuse ISPF Session: Specify true if you have translators that use a call method of ISPF command or EXEC and wish to avoid the overhead of repeated session setup and teardown. Note: This option is for advanced use cases only.

team.enterprise.build.ant.simulationModeBinaryCheck

true

false

 Verify build outputs during a simulation build: Specify true to updates the simulation registry to reflect whether each output is present. Specify false to reduce simulation build overhead by assuming all build outputs are present and correct.

team.enterprise.build.dependency.needToDeleteOutputs

true

false

 Delete obsolete outputs: Specify true to delete outputs that are no longer produced by any buildable files.

team.enterprise.build.dependency.preprocessUpdateF

integer

 Frequency of updates to the number of buildable files pre-processed in the build report contribution summary: Specify the number of files to preprocess before updates are made in the Build Result editor. The default is 100.

team.enterprise.build.dependency.trustInputs

true

false

 Trust build inputs: Specify true to trust the files that are already loaded in zFolder data sets. When SCM metadata is not available for any reason, and this property is set to true, existing files loaded into zFolder data sets are considered to be valid and will not be overwritten when a workspace load is processed. New SCM metadata will be generated for the files as part of this process.

The trust inputs option can significantly decrease the load time on z/OS when the SCM configuration directory needs to be cleared for housekeeping.

The default value is false. So, data set contents are not trusted unless they can be validated by SCM metadata, and if that SCM metadata is not available, the files will be reloaded.

This property is especially useful when running a build across multiple build agents or installing a new build agent.

team.enterprise.build.dependency.trustOutputs

true

false

 Trust build outputs: Specify true to have the build run on the premise that you did not delete or modify the outputs that were created in previous builds. This option improves performance when you rebuild because you skip unnecessary checks for missing or changed outputs.

team.enterprise.build.impacts.disableAlwaysBuildQueries

true

false

 Calculate impacts of files being forced to be built: Specify false to do the calculation. Specify true to skip the calculation. When impact calculations are enabled, they are also run on files that are forced to be rebuilt. For example, files in a mandatory subset.

team.enterprise.build.impacts.disableInputQueries

true

false

 Calculate impacted dependencies stored in the repository: Specify false to do the calculation. Specify true to skip the calculation. This corresponds to reason code 2 in the build report: One or more dependencies stored in the repository have changed.

team.enterprise.build.impacts.disableParserOutputQueries

true

false

 Calculate impacted dependencies not in the repository: Specify false to do the calculation. Specify true to skip the calculation. This corresponds to reason code 3 in the build report: One or more dependencies not in the repository, such as generated input files, have changed.

team.enterprise.build.suppressBuildMapLinks

true

false

 Publish build map links: Specify true to publish build map links on the External Links tab of the build.

com.ibm.team.build.logging

true

false

 Live logging: Specify true to enable live logging for the build

com.ibm.team.build.logging.level

ERROR

WARNING

INFO

DEBUG

VERBOSE

 Messaging level for live logging: Specifies the level of messages that live logging issues when enabled

com.ibm.team.build.logging.retry

 integer (between 0 and 3) Number of retries when an error tries to publish messages: Specifies the number of retries in case of any error trying to publish messages

com.ibm.team.build.logging.toolkitver.skip

true

false

 Skip toolkit version level check: Specify true skip the checking of the version level of the build target toolkit
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.enterprise.build.ant.buildableSubsetSlug
    • team.enterprise.build.ant.createAllDependencySets
    • team.enterprise.build.dependency.previewBuild
  • The following is a list of reserved properties names which can not be specified:
    • team.enterprise.build.ant.mandatorySubsetIsTransitory
    • team.enterprise.build.ant.postBuildPropReturns
    • team.enterprise.build.ant.preBuildPropReturns
    • team.enterprise.build.dependency.realToDeleteOutputs
    • team.enterprise.build.mandatorySubset.cleanupPolicy
    • team.enterprise.build.subset.cleanup.allowedInPersonal
    • team.enterprise.build.subset.cleanup.allowedInPreview
    • team.enterprise.build.subset.cleanupPolicy
    • com.ibm.team.build.logging.listener

teamBuildProperty Element - IBM i Deployment Build

The following table describes the valid values for teamBuildProperty element attributes for an IBM® i Deployment build:

name value Description

team.deploy.common.action

""

deployMain

loadMain

rollbackMain
Deploy type: Specify the type of deployment to perform. Valid values are:
Value Description
"" Load and deploy (a blank or empty value).
deployMain Deploy.
loadMain Load.
rollbackMain Rollback.
This property should be included as a Schedule Team Property.

team.deploy.common.deploy.postCommand

  

Deploy post-command: Command to be executed after deployment.

team.deploy.common.deploy.preCommand

  

Deploy pre-command: Command to be executed prior to deployment.

team.deploy.common.load.ftp.hostname

  

Host name: FTP host name.

team.deploy.common.load.ftp.passwordFile

  

Password file: FTP password file.

team.deploy.common.load.ftp.userid

  

User ID: FTP user ID.

team.deploy.common.load.postCommand

  

Load post-command: Command to be executed after load.

team.deploy.common.load.preCommand

  

Load pre-command: Command to be executed prior to load.

team.deploy.common.loadMethod

Copy

ftp
Load method: Specify the type of load method to use and the appropriate command and/or FTP properties. When Copy is specified, the FTP host name, user ID, and password file attributes must not be specified. When ftp is specified, the FTP host name, user ID, and password file attributes are required. Valid values are:
Value Description
Copy Copy libraries on this system.
ftp FTP libraries from another system.

team.deploy.common.localPackageRoot.dir

  

Deployed package root directory:* Local package root directory.

team.deploy.common.packageLabel

   Package: Specify the label of the target packaging build result. This property should be included as a Schedule Team Property.

team.deploy.common.packagedefinitionUUID

  

Package definition:* Specify the ID of the packaging build definition.

team.deploy.common.publishCumulativeDeploy

true

false

 Publish cumulative deploy manifest: Specify true to publish the cumulative deployment manifest file in the deployment result.

team.deploy.common.publishDeltaDeploy

true

false

 Publish delta deploy manifest: Specify true to publish the delta deployment manifest file in the deployment result.

team.deploy.common.publishRollbackManifest

true

false

 Publish rollback manifest: Specify true to publish the rollback manifest file in the deployment result.

team.deploy.common.remotePackageRoot.dir

  

Original package root directory:* Remote package root directory.

team.deploy.common.restoreMappingList

  
From Library/To Library: Specify the names of the libraries created by the packaging build, and where to deploy them, in the restore mapping table. Specify a comma separated list of From/To paired library names. For example:
fromLibrary,toLibrary

team.deploy.common.rollback.maximumKeep

integer

Maximum number of rollbacks to keep: Specify an integer value for the number of rollbacks to keep.

team.deploy.common.rollback.multipleAllowed

true

false

 Allow multiple rollbacks: Specify true to allow your team to roll back a saved package that was successfully deployed. The default is false. Note: Ignored for agents older than 5.0.1.

team.deploy.common.rollback.postCommand

  

Rollback post-command: Command to be executed after roll back.

team.deploy.common.rollback.preCommand

  

Rollback pre-command: Command to be executed prior to roll back.

team.deploy.ibmi.intermediateSaveFileLibrary

  

IBM i intermediate save file library:* Specify a working library on the IBM i server to temporarily store objects.

team.deploy.ibmi.pfRestoreMethod

REPLACE

MIGRATE

USRCMD
Rules for deploying physical files: Specify how to handle physical file (*FILE:PF-DTA) objects during deployment.
Value Description
REPLACE Overwrite physical file objects with source objects.
MIGRATE Keep existing data in physical files.
USRCMD Keep existing data in physical files using command specified by pfRestoreCommand.

team.deploy.ibmi.pfRestoreUsrCmd

  

User-defined command to deploy each physical file: Specify the CL command to be executed for each file. When this option is selected, the substitution variables &A, &F, &L, &N, &T, and &S are supported in the build command.

team.deploy.ibmi.savePfForRollback

true

false

 Save physical files in rollback archive before deployment: Specify true to save physical files in a rollback archive before deployment to save a backup of your physical files in case errors occur during the deployment process. The default is true. If an error occurs, the original objects can be restored by requesting a rollback.
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.deploy.common.definition.version
    • team.deploy.common.filesystem
    • team.deploy.common.load.cd.deployment.useBuildAgentSettings
    • team.deploy.common.load.cd.localIp
    • team.deploy.common.load.cd.localPassword
    • team.deploy.common.load.cd.localPort
    • team.deploy.common.load.cd.localUserId
    • team.deploy.common.load.cd.nodeName
    • team.deploy.common.load.cd.packaging.useBuildAgentSettings
    • team.deploy.common.load.cd.remotePassword
    • team.deploy.common.load.cd.remoteUserId
    • team.deploy.common.openSummaryWorkItem
    • team.deploy.common.restoreMappingPath
    • team.deploy.luw.runtimeRoot.dir
  • The following is a list of reserved properties names which can not be specified:
    • team.deploy.common.applicationDescription
    • team.deploy.common.applicationName
    • team.deploy.common.isCompletePackage
    • team.deploy.common.version team.deploy.zos.script
    • team.enterprise.ibmi.ASPName
    • team.enterprise.ibmi.setASP

teamBuildProperty Element - IBM i Dependency Build

The following table describes the valid values for teamBuildProperty element attributes for an IBM i Dependency build:

name value Description

team.enterprise.build.ant.alwaysRunPostBuildFile

true

false

 Always run post-build script: Specify true to run the specified post-build ant script whether or not the build was successful. The default is false, the specified post-build ant script will only be run if the build was successful.

team.enterprise.build.ant.buildChangesOnly

true

false

 Build changed items only: Specify true to build only the items that have changed since the last successful build. Specify false to build all items found in the workspace. The default is true.

team.enterprise.build.ant.buildableSubset

  

Build subset: Specify the name of an existing build subset. Build subsets specify a group of buildable items that will be included when executing a dependency build.

team.enterprise.build.ant.fullMinimumLoad

true

false

 Perform full minimum load: Specify true to load all items that recently changed or that depend on items that changed since the last successful build. This option is only valid for personal builds. Items will be loaded from the workspace specified on the build request to the resource prefix specified on the build request.

team.enterprise.build.ant.mandatorySubset

  

Mandatory Subset: If there are files to be included in each build for this build definition, specify the name of the subset containing the files that are required to be included in this build. The files in the mandatory subset are always built, even if they are not changed.

team.enterprise.build.ant.mandatorySubset.useInPersonal

true

false

 Include this mandatory subset in personal builds by default: Specify true to include the mandatory subset in personal builds.

team.enterprise.build.ant.postBuildFile

  

Post-build script: Specify the path to the post-build script on the build machine. This can be an absolute path on the build machine or may be a path relative to the current directory of the build engine process.

team.enterprise.build.ant.preBuildFile

  

Pre-build script: Specify the path to the pre-build script on the build machine. This can be an absolute path on the build machine or may be a path relative to the current directory of the build engine process.

team.enterprise.build.ant.simulationModeBinaryCheck

true

false

 Verify build outputs during a simulation build: Specify true to updates the simulation registry to reflect whether each output is present. Specify false to reduce simulation build overhead by assuming all build outputs are present and correct.

team.enterprise.build.dependency.preprocessUpdateF

integer

Frequency of updates to the number of buildable files pre-processed in the build report contribution summary: Specify the number of files to preprocess before updates are made in the Build Result editor. The default is 10.

team.enterprise.build.dependency.trustOutputs

true

false

 Trust build outputs: Specify true to have the build run on the premise that you did not delete or modify the outputs that were created in previous builds. This option improves performance when you rebuild because you skip unnecessary checks for missing or changed outputs.

team.enterprise.build.impacts.disableAlwaysBuildQueries

true

false

 Calculate impacts of files being forced to be built: Specify false to do the calculation. Specify true to skip the calculation. When impact calculations are enabled, they are also run on files that are forced to be rebuilt. For example, files in a mandatory subset.

team.enterprise.build.impacts.disableParserOutputQueries

true

false

 Calculate impacted dependencies not in the repository: Specify false to do the calculation. Specify true to skip the calculation. This corresponds to reason code 3 in the build report: One or more dependencies not in the repository, such as generated input files, have changed.

team.enterprise.build.suppressBuildMapLinks

true

false

 Publish build map links: Specify true to publish build map links on the External Links tab of the build.

team.enterprise.build.ibmi.postCommand

  

Post-command: Specify an IBM i command to run after the build script runs.

com.ibm.team.enterprise.ibmi.build.AppendLoadObjLibraries

true

false

 Append load and object libraries from the build definition: Specify true to append load and object libraries from the build definition for personal builds.

com.ibm.team.enterprise.ibmi.build.ant.failOnError

true

false

 Stop and fail the build (compile error level): Specify true to fail the build when the generated events file contains a severity level that meets or exceeds the value specified with the com.ibm.team.enterprise.ibmi.build.ant.failOnError.level attribute.

com.ibm.team.enterprise.ibmi.build.ant.failOnError.level

integer

Stop and fail the build (compile error level): Specify the error level found in the generated events file that will trigger a build failure.

com.ibm.team.enterprise.ibmi.build.ant.icmd.failOnError

true

false

 Stop and fail the build (i command): Specify true to fail the build when an IBM i command completes with a severity level that meets or exceeds the value specified with the com.ibm.team.enterprise.ibmi.build.ant.icmd.failOnError.level attribute.

com.ibm.team.enterprise.ibmi.build.ant.icmd.failOnError.level

integer

Stop and fail the build (i command level): Specify the error level received for IBM i command that will trigger a build failure.

com.ibm.team.enterprise.ibmi.build.searchPath

  

Search path: Specify a search path for the build to use as the library list for the build.

com.ibm.team.build.logging

true

false

 Live logging: Specify true to enable live logging for the build

com.ibm.team.build.logging.level

ERROR

WARNING

INFO

DEBUG

VERBOSE

 Messaging level for live logging: Specifies the level of messages that live logging issues when enabled

com.ibm.team.build.logging.retry

 integer (between 0 and 3) Number of retries when an error tries to publish messages: Specifies the number of retries in case of any error trying to publish messages

com.ibm.team.build.logging.toolkitver.skip

true

false

 Skip toolkit version level check: Specify true skip the checking of the version level of the build target toolkit
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.enterprise.build.ant.buildableSubsetSlug
    • team.enterprise.build.ant.createAllDependencySets
    • team.enterprise.build.dependency.previewBuild
    • com.ibm.team.enterprise.ibmi.build.referencedLibraries
  • The following is a list of reserved properties names which can not be specified:
    • team.enterprise.build.ant.mandatorySubsetIsTransitory
    • team.enterprise.build.ant.postBuildPropReturns
    • team.enterprise.build.ant.preBuildPropReturns
    • team.enterprise.build.dependency.needToDeleteOutputs
    • team.enterprise.build.dependency.realToDeleteOutputs
    • team.enterprise.build.mandatorySubset.cleanupPolicy
    • team.enterprise.build.subset.cleanup.allowedInPersonal
    • team.enterprise.build.subset.cleanup.allowedInPreview
    • team.enterprise.build.subset.cleanupPolicy
    • com.ibm.team.enterprise.ibmi.build.appendReferencedLibraries
    • com.ibm.team.build.logging.listener

teamBuildProperty Element - IBM i Packaging Build

The following table describes the valid values for teamBuildProperty element attributes for an IBM i Packaging build:

name value Description

team.enterprise.packaging.includeImpactedObjects

true

false

 Include Impacted Outputs: Specify true to include indirect outputs for work item packaging (e.g. linked load modules, bound service programs). This property should be included as a Schedule Team Property.

team.enterprise.packaging.packagedWorkitems

   Work Items: Specify a comma separated list of work items IDs whose outputs should be packaged. This property should be included as a Schedule Team Property.

team.package.common.buildDefinition.uuid

  

Build definition: Specify the name of a build definition to be packaged.

team.package.common.exclude.binaries

  
Resource filters to exclude: Specify a generic filter or specific objects, and then indicate a library, an object, and a type in the following format:
library(object) OBJTYPE(type)

A list of resource filters can be specified with each separated by a comma.

team.package.common.include.binaries

  
Resource filters to include: Specify a generic filter or specific objects, and then indicate a library, an object, and a type in the following format:
library(object) OBJTYPE(type)

A list of resource filters can be specified with each separated by a comma.

team.package.common.isAutoClean

true

false

 Auto clean: Specify true to delete a package from the package root directory so that you have more package space available.

team.package.common.isConcurrentSafe

true

false

 Allow concurrent package requests: Specify true to allow multiple packaging builds to run concurrently (not allowed for agents older than 5.0.2).

team.package.common.isIntermediatesPublished

true

false

 Publish intermediate files: Specify true to publish intermediate packaging results.

team.package.common.isManifestPublished

true

false

 Publish manifest: Specify true to publish packaging manifest.

team.package.common.isPackagePublished

true

false

 Publish package: Specify true to publish packaging results.

team.package.common.packageBinariesSinceTimestamp

   Time Stamp: Omit ship list resources older than this time stamp (format: yyyyMMdd-HHmmssSSSS or leave blank to ignore time stamps). This property should be included as a Schedule Team Property.

team.package.common.packageRoot.dir

  

Package root directory:* Specify a directory on the build systems where you want to store all packages.

team.package.common.postPackageCommand

  

Package post-command: Specify a command to run on the build system after packaging.

team.package.common.prePackageCommand

  

Package pre-command: Specify a command to run on the build system before packaging.

team.package.common.workItemPackaging

   Packaging Type: Specify true to calculate package contents from work items. Specify false to calculate package contents from a list of resources. This property should be included as a Schedule Team Property.

team.package.ibmi.intermediateSaveFileLibrary

  

IBM i intermediate save file library:* Specify a library name to temporarily store objects on the IBM i server.

team.package.ibmi.savefileOptions

   IBM i save file options: Specify a TGTRLS VRM_release_level, where VRM_release_level is a valid target release for saving objects on the packaging host; for example, *CURRENT, *PRV, or V6R1M0. If you do not specify this option, the objects are saved at TGTRLS(*CURRENT).

team.package.restore.mapping

  
From Library/To Library: Specify the libraries to package and where to deploy them in the restore mapping table. Specify a comma separated list of From/To paired library names. For example:
fromLib,toLib,fromLib2,toLib2
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.enterprise.packaging.deleteObsoleteOutputs
    • team.package.common.definition.version
    • team.package.common.filesystem
    • team.package.common.openSummaryWorkItem
    • team.package.luw.buildRoot.dir
    • team.package.zos.script
  • The following is a list of reserved properties names which can not be specified:
    • team.enterprise.ibmi.ASPName
    • team.enterprise.ibmi.setASP
    • team.package.common.applicationDescription
    • team.package.common.applicationName
    • team.package.common.buildSnapshotId
    • team.package.common.excludeFilePath
    • team.package.common.isCompletePackage
    • team.package.common.restoreMappingPath
    • team.package.common.shiplist.option
    • team.package.common.shiplistFilePath
    • team.package.common.timestamp.option
    • team.package.common.version
    • team.package.common.workitem.option
    • team.package.ucd.component
    • team.package.ucd.generate
    • team.package.ucd.tk.script
    • team.package.ucd.type
    • team.package.ucd.versionName.convention
    • team.package.ucd.versionName.prefix
    • team.package.zos.buildDefinition.uuid
    • team.package.zos.optional.shiplistFilePath

teamBuildProperty Element - IBM i Promotion Build

The following table describes the valid values for teamBuildProperty element attributes for an IBM i Promotion build:

name value Description

team.enterprise.promotion.component.suppressTargetBuild

true

false

Engineering Workflow Management runs a build on a target build definition after a component promotion by default. Use this property to prevent the build from requesting the target build.

team.enterprise.promotion.ibmi.postCommand

  

Post-command: Specify an IBM i command to run after the build script runs.

team.enterprise.promotion.ibmi.preCommand

  

Pre-command: Specify an IBM i command to run before the build script runs.

team.enterprise.promotion.promotionUserId

  

User ID used during scheduled component promotions to promote source and update the summary work item. You can use this property to specify the user ID that runs the promotion. The default user ID for promotions is ADMIN.

team.enterprise.promotion.suppressBuildMapLinks

true

false

Engineering Workflow Management publishes all build maps that are promoted in the build result by default. For performance reasons, you can use this property to prevent the build map links from being published in the build result.

com.ibm.team.enterprise.promotion.skipTimestampCheck

true

false

 Skip timestamp check when build outputs are promoted: The time stamp check verifies that the built objects that you are promoting match the objects that are specified in the build map. If you know that the built objects changed and you want to promote anyway, specify true to skip the timestamp check when promoting build outputs.
Note:
The following is a list of reserved properties names which can not be specified unless overridden:
  • team.promotion.filesystem

teamBuildProperty Element - Ant with Enterprise Extensions Publishing

The following table describes the valid values for teamBuildProperty element attributes for the Ant with Enterprise Extensions publishing facility:

name value Description

teamz.build.publishoutputs

true

false

 Publish job output logs: Specify true to have designated compiler listings published in the build results.

teamz.build.publishoutputs.erroronly

true

false

 Publish only when an error occurred: Specify true to limit the overhead of log publishing by only publishing listings when an error occurs in the build process.

teamBuildProperty Element - z/OS Packaging Build

The following table describes the valid values for teamBuildProperty element attributes for an z/OS Packaging build:

name value Description

team.enterprise.packaging.deleteObsoleteOutputs

true

false

 Delete obsolete work item outputs: Specify true to analyze the change sets of the work items being packaged and locate outputs no longer being created by the files in the change sets. There are limitations to the deletion of outputs.

team.enterprise.packaging.includeImpactedObjects

true

false

 Include Impacted Outputs: Specify true to include indirect outputs for work item packaging (e.g. linked load modules, bound service programs). This property should be included as a Schedule Team Property.

team.enterprise.packaging.packagedWorkitems

   Work Items: Specify a comma separated list of work items IDs whose outputs should be packaged. This property should be included as a Schedule Team Propertyy.

team.package.common.buildDefinition.uuid

  

Build definition: Specify the name of a build definition to be packaged.

team.package.common.exclude.binaries

  

Resource filters to exclude: Specify a generic filter or a specific data set and member by name. To specify a generic filter, indicate the data set name and member name pattern in the following format:

DATA.SET.NAME(MBR) OBJTYPE(*)

To specify a specific data set and member by name, indicate the data set name and member name in the following format:

DSN1(MBR1)

A list of resource filters can be specified with each separated by a comma.

team.package.common.include.binaries

  

Resource filters to include: Specify a generic filter or a specific data set and member by name. To specify a generic filter, indicate the data set name and member name pattern in the following format:

DATA.SET.NAME(MBR) OBJTYPE(*)

To specify a specific data set and member by name, indicate the data set name and member name in the following format:

DSN1(MBR1)

A list of resource filters can be specified with each separated by a comma.

team.package.common.isAutoClean

true

false

 Auto clean: Specify true to delete a package from the package root directory so that you have more package space available.

team.package.common.isConcurrentSafe

true

false

 Allow concurrent package requests: Specify true to allow multiple packaging builds to run concurrently (not allowed for agents older than 5.0.2).

team.package.common.isIntermediatesPublished

true

false

 Publish intermediate files: Specify true to publish intermediate packaging results.

team.package.common.isManifestPublished

true

false

 Publish manifest: Specify true to publish packaging manifest.

team.package.common.isPackagePublished

true

false

 Publish package: Specify true to publish packaging results.

team.package.common.packageBinariesSinceTimestamp

   Time Stamp: Omit ship list resources older than this time stamp (format: yyyyMMdd-HHmmssSSSS or leave blank to ignore time stamps). This property should be included as a Schedule Team Property.

team.package.common.packageRoot.dir

  

Package root directory:* Specify a directory on the build systems where you want to store all packages.

team.package.common.postPackageCommand

  

Package post-command: Specify a command to run on the build system after packaging.

team.package.common.prePackageCommand

  

Package pre-command: Specify a command to run on the build system before packaging.

team.package.common.workItemPackaging

   Packaging Type: Specify true to calculate package contents from work items. Specify false to calculate package contents from a list of resources. This property should be included as a Schedule Team Property.

team.package.restore.mapping

  

From Data Set/To Data Set: Specify the PDS to package and where to deploy them in the restore mapping table. Specify a comma separated list of From/To paired data set names. For example:

FROM.DSN0,TO.DSN0,FROM.DSN1,TO.DSN1

team.package.ucd.component

   UrbanCode® Deploy component name: Specify the name of the UrbanCode Deploy component for which the versions are being created.

team.package.ucd.generate

true

false

 Generate UrbanCode Deploy package: If true is specified, UrbanCode Deploy generates a component version. If false is specified, a ship list is generated that UrbanCode Deploy can use later to generate a component version.

team.package.ucd.tk.script

  

UrbanCode Deploy Toolkit script: Specify the path name of the toolkit script that creates z/OS versions. For example: /var/ucd611/agent/bin/buztool.sh.

team.package.ucd.type

true

false

 UrbanCode Deploy package type: Specify true to generate an UrbanCode Deploy package from this package definition.

team.package.ucd.versionName.convention

PROMPT

TIMESTAMP

WORKITEM
UrbanCode Deploy version naming convention: Specify one of the following choices:
Choice Description
PROMPT You specify the component version name when you request the package.
TIMESTAMP Creates a component version name based on the time of the package request.
WORKITEM The resulting component version name is the first work item number selected on the package request followed by a timestamp.

team.package.ucd.versionName.prefix

   Prefix for UrbanCode Deploy version name: Specified text is prepended to the version name, regardless of which naming convention you select.

team.package.zos.script

  

z/OS ISPF gateway script:* Specify the path to the z/OS UNIX System Services (USS) shell script startispf.sh, which is used for running REXX EXEC files. The location of this shell script depends on how you configured your Build System Toolkit on z/OS. The default directory is: /etc/jazz601/ccm/startispf.sh.
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.package.common.definition.version
    • team.package.common.filesystem
    • team.package.common.openSummaryWorkItem
    • team.package.ibmi.intermediateSaveFileLibrary
    • team.package.ibmi.savefileOptions
    • team.package.luw.buildRoot.dir
  • The following is a list of reserved properties names which can not be specified:
    • team.enterprise.ibmi.ASPName
    • team.enterprise.ibmi.setASP
    • team.package.common.applicationDescription
    • team.package.common.applicationName
    • team.package.common.buildSnapshotId
    • team.package.common.excludeFilePath
    • team.package.common.isCompletePackage
    • team.package.common.restoreMappingPath
    • team.package.common.shiplist.option
    • team.package.common.shiplistFilePath
    • team.package.common.timestamp.option
    • team.package.common.version
    • team.package.common.workitem.option
    • team.package.zos.buildDefinition.uuid
    • team.package.zos.optional.shiplistFilePath

teamBuildProperty Element - z/OS Promotion Build

The following table describes the valid values for teamBuildProperty element attributes for an z/OS Promotion build:

name value Description

com.ibm.team.enterprise.promotion.skipTimestampCheck

true

false

 Skip timestamp check when build outputs are promoted: The time stamp check verifies that the built objects that you are promoting match the objects that are specified in the build map. If you know that the built objects changed and you want to promote anyway, specify true to skip the timestamp check when promoting build outputs.

team.enterprise.promotion.promotionUserId

  

User ID used during scheduled component promotions to promote source and update the summary work item. You can use this property to specify the user ID that runs the promotion. The default user ID for promotions is ADMIN.
team.enterprise.promotion.component.suppressTargetBuild

true

false

 Engineering Workflow Management runs a build on a target build definition after a component promotion by default. Use this property to prevent the build from requesting the target build.

team.enterprise.promotion.suppressBuildMapLinks

true

false

Engineering Workflow Management publishes all build maps that are promoted in the build result by default. For performance reasons, you can use this property to prevent the build map links from being published in the build result.

team.promotion.zos.script

   z/OS ISPF gateway script:* Specify the path to the z/OS UNIX System Services (USS) shell script startispf.sh, which is used for running REXX EXEC files. The location of this shell script depends on how you configured your Build System Toolkit on z/OS. The default directory is: /etc/jazz601/ccm/startispf.sh.
Note:
The following is a list of reserved properties names which can not be specified unless overridden:
  • team.promotion.filesystem

teamBuildProperty Element - Enterprise Extensions Publishing

The following table describes the valid values for teamBuildProperty element attributes for the Enterprise Extensions publishing facility:

name value Description

team.enterprise.build.publishoutputs

true

false

 Publish job output logs: Specify true to have designated compiler listings published in the build results.

team.enterprise.build.publishoutputs.erroronly

true

false

 Publish only when an error occurred: Specify true to limit the overhead of log publishing by only publishing listings when an error occurs in the build process.

team.enterprise.build.publishoutputs.successfulLogsAsZips

true

false

 Publish successful logs as zip files (one zip file per 100 logs): Specify true to limit the overhead of log publishing by consolidating logs into a single compressed zip file.

teamBuildProperty Element - Jazz Source Control for an Ant Build

The following table describes the valid values for teamBuildProperty element attributes for Jazz® Source Control for an Ant build:

name value Description

team.scm.acceptBeforeFetch

true

false

 Accept latest changes before loading: Specify true to accept incoming changes to the workspace before loading the workspace to the fetch destination (creates a snapshot of the build workspace).

team.scm.buildOnlyIfChanges

true

false

 Build only if there are changes accepted: Specify true to build only if there are changes delivered to the build stream that have not been accepted into the build workspace. This option is only applicable for scheduled builds.

team.scm.componentLoadRules

  

Load rules: To define a subset of component files and folders for the build to load, specify the path to the component load rules file. The path should include the component name, project name, folder name(s), and the load rule file name. For example:/ComponentName/ProjectName/RulesFolder/RulesFile.loadrules.

team.scm.createFoldersForComponents

true

false

 Create folders for components: Specify true to create component level folders during the load. Normally, folders are created starting at the project level.

team.scm.deleteDestinationBeforeFetch

true

false

 Delete directory before loading: Specify true to delete source control metadata from the load directory before the workspace is loaded. Source control metadata stores information about the files that you load from Engineering Workflow Management. When a build fails because of corrupted metadata, specify true to clean up the metadata and resolve the issue. However, when metadata is not corrupted and you select this option, your build might take longer to complete. Select this option only if you want to clean up the load directory and its associated metadata prior to loading the workspace.

team.scm.fetchDestination

  

Load directory:* Specify the path to the directory on the build machine where workspace files should be loaded.

Note: It is advised to avoid using blanks or $ in the path as these characters (or their national language equivalents) can cause inconsistent results.

team.scm.loadComponents

  

Components to exclude: Specify a comma separated list of component names that are to be excluded from the load process. This option can be used to restrict which components are loaded during the build.

team.scm.maxContentThreads

integer

Maximum content threads: Specify a positive integer value for the number of simultaneous transfers that can occur at one time. The ant attribute value cannot be negative. Default value is 10.

team.scm.workspaceUUID

  

Workspace:* Specify the name of the build workspace.
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.scm.includeComponents
  • The following is a list of reserved properties names which can not be specified:
    • team.scm.changesAccepted
    • team.scm.snapshotUUID

teamBuildProperty Element - Jazz Source Control for a Dependency Build

The following table describes the valid values for teamBuildProperty element attributes for Jazz Source Control for a Dependency Build:

name value Description

team.enterprise.build.ant.fetchAll

true

false

 Load workspace to the resource with the resource prefix at the beginning of the build: Specify true to have artifacts stored in an enterprise file system (like PDSE on z/OS or Library on IBM i) to be loaded to the resources defined with the resource prefix at the beginning of the build.

team.enterprise.build.ant.fetchWorkspaceBeforeBuild

true

false

 Load workspace to the load directory at the beginning of the build: Specify true to have artifacts stored in the Hierarchical File System to be loaded to the load directory at the beginning of the build.

team.enterprise.scm.acceptBeforeFetch

true

false

 Accept latest changes before loading: Specify true to accept incoming changes to the workspace before loading the workspace to the fetch destination (creates a snapshot of the build workspace).

team.enterprise.scm.buildOnlyIfChanges

true

false

 Build only if there are changes accepted: Specify true to build only if there are changes delivered to the build stream that have not been accepted into the build workspace. This option is only applicable for scheduled builds.

team.enterprise.scm.componentLoadRules

  

Load rules: To define a subset of component files and folders for the build to load, specify the path to the component load rules file. The path should include the component name, project name, folder name(s), and the load rule file name. For example:

/ComponentName/ProjectName/RulesFolder/RulesFile.loadrules

team.enterprise.scm.createFoldersForComponents

true

false

 Create folders for components: Specify true to create component level folders during the load. Normally, folders are created starting at the project level.

team.enterprise.scm.deleteDestinationBeforeFetch

true

false

 Delete directory before loading: Specify true to delete source control metadata from the load directory before the workspace is loaded. Source control metadata stores information about the files that you load from Engineering Workflow Management. When a build fails because of corrupted metadata, specify true to clean up the metadata and resolve the issue. However, when metadata is not corrupted and you select this option, your build might take longer to complete. Select this option only if you want to clean up the load directory and its associated metadata prior to loading the workspace.

team.enterprise.scm.fetchDestination

  

Load directory:* Specify the path to the directory on the build machine where workspace files should be loaded.

Note: It is advised to avoid using blanks or $ in the path as these characters (or their national language equivalents) can cause inconsistent results.

team.enterprise.scm.loadComponents

  

Components to exclude: Specify a comma separated list of component names that are to be excluded from the load process. This option can be used to restrict which components are loaded during the build.

team.enterprise.scm.log.loading

true

false

 Log loading: Specify true to create a log file and attach it to the build results on the Logs tab. The log file shows all of the commands that run to perform the required loading.

team.enterprise.scm.maxContentThreads

integer

Maximum content threads: Specify a positive integer value for the number of simultaneous transfers that can occur at one time. The ant attribute value cannot be negative. Default value is 10.

This property controls the number of threads used to load source control files into z/OS data sets. When this property is specified, it overrides the value of the team.scm.maxContentThreads property. The two properties can be used in conjunction: team.enterprise.scm.maxContentThreads to control the number of threads used to load data sets and team.scm.maxContentThreads to control the number of threads used to load USS contents. If only the team.scm.maxContentThreads property is specified, that value is used for the thread count for both data sets and USS contents. If only the team.enterprise.scm.maxContentThreads property is specified, that value is used for the thread count for data sets; the default thread count will be used for USS contents.

team.enterprise.scm.resourcePrefix

  

Resource prefix:* Specify the high-level qualifier for data set names. The name prefix to be used when allocating data sets.

Note: It is advised to avoid using blanks or $ in the prefix as these characters (or their national language equivalents) can cause inconsistent results.

team.enterprise.scm.resourceTeamPrefix

  

Resource prefix:* Specify the high-level qualifier for data set names. The name prefix to be used when allocating data sets.

Note: It is advised to avoid using blanks or $ in the prefix as these characters (or their national language equivalents) can cause inconsistent results.

team.enterprise.scm.teamWorkspaceUUID

  

Workspace:* Specify the name of the build workspace.

team.enterprise.scm.workspaceUUID

  

Workspace:* Specify the name of the build workspace. This property must be set together with the teamz.scm.workspaceUUID property. The two properties cannot be dissociated.

teamz.scm.workspaceUUID

  

Workspace:* Specify the name of the build workspace. This property must be set together with the team.enterprise.scm.workspaceUUID property. The two properties cannot be dissociated.
Note:
The following is a list of reserved properties names which can not be specified unless overridden:
  • team.enterprise.scm.includeComponents

teamBuildProperty Element - Jazz Source Control for an IBM i Command Line Build

The following table describes the valid values for teamBuildProperty element attributes for Jazz Source Control for an IBM i Command Line build:

name value Description

team.scm.acceptBeforeFetch

true

false

 Accept latest changes before loading: Specify true to accept incoming changes to the workspace before loading the workspace to the fetch destination (creates a snapshot of the build workspace).

team.scm.buildOnlyIfChanges

true

false

 Build only if there are changes accepted: Specify true to build only if there are changes delivered to the build stream that have not been accepted into the build workspace. This option is only applicable for scheduled builds.

team.scm.clearDestinationBeforeFetch

true

false

 Clear libraries before loading: Specify true to execute the CLRLIB command. The CLRLIB command will clear each of the mapped libraries in the repository workspace properties before i Projects artifacts in the repository workspace (for example, source physical files, source members, and save files) are loaded to those mapped libraries.

team.scm.fetchChangesOnly

true

false

Load latest changes only: Specify true to load those artifacts that are accepted into the build workspace when the build runs.

Load all workspace contents: Specify false to load all workspace artifacts every time the build runs.

team.scm.workspaceUUID

  

Workspace:* Specify the name of the build workspace.
Note:
The following is a list of reserved properties names which can not be specified unless overridden:
  • team.scm.componentLoadRules
  • team.scm.deleteDestinationBeforeFetch
  • team.scm.fetchDestination

teamBuildProperty Element - Jazz Source Control for an IBM i Continuous Load Build

The following table describes the valid values for teamBuildProperty element attributes for Jazz Source Control for an IBM i Continuous Load build:

name value Description

team.scm.workspaceUUID

  

Workspace:* Specify the name of the build workspace.
Note:
The following is a list of reserved properties names which can not be specified:
  • team.scm.acceptBeforeFetch
  • team.scm.buildOnlyIfChanges
  • team.scm.clearDestinationBeforeFetch
  • team.scm.fetchChangesOnly

teamBuildProperty Element - Jazz Source Control for an Ant with Enterprise Extensions Build

The following table describes the valid values for teamBuildProperty element attributes for Jazz Source Control for an Ant with Enterprise Extensions build:

name value Description

teamz.scm.acceptBeforeFetch

true

false

 Accept latest changes before loading: Specify true to accept incoming changes to the workspace before loading the workspace to the fetch destination (creates a snapshot of the build workspace).

teamz.scm.buildOnlyIfChanges

true

false

 Build only if there are changes accepted: Specify true to build only if there are changes delivered to the build stream that have not been accepted into the build workspace. This option is only applicable for scheduled builds.

teamz.scm.dataset.prefix

  

Data set prefix:* Specify the high-level qualifier for data set names. The name prefix to be used when allocating data sets.

Note: It is advised to avoid using blanks or $ in the prefix as these characters (or their national language equivalents) can cause inconsistent results.

teamz.scm.deleteDestinationBeforeFetch

true

false

 Delete directory before loading: Specify true to delete source control metadata from the load directory before the workspace is loaded. Source control metadata stores information about the files that you load from Engineering Workflow Management. When a build fails because of corrupted metadata, specify true to clean up the metadata and resolve the issue. However, when metadata is not corrupted and you select this option, your build might take longer to complete. Select this option only if you want to clean up the load directory and its associated metadata prior to loading the workspace.

teamz.scm.fetchDestination

  

Load directory:* Specify the path to the directory on the build machine where workspace files should be loaded.

Note: It is advised to avoid using blanks or $ in the path as these characters (or their national language equivalents) can cause inconsistent results.

teamz.scm.workspaceUUID

  

Workspace:* Specify the name of the build workspace.
Note:

The following is a list of reserved properties names which can not be specified:

  • teamz.scm.componentLoadRules
  • teamz.scm.dataset.originalprefix
  • teamz.scm.dataset.teamprefix

teamBuildProperty Element - UrbanCode Deploy

The following table describes the valid values for teamBuildProperty element attributes for a build using UrbanCode Deploy:

name value Description

team.udeploy.personalBuilds

true

false

 Personal builds: Specify true to enable for personal builds.
Note:
The following is a list of reserved properties names which can not be specified unless overridden:
  • team.udeploy.debug
  • team.udeploy.timeout

teamBuildProperty Element - Unix Deployment Build

The following table describes the valid values for teamBuildProperty element attributes for a Unix Deployment build:

name value Description

team.deploy.common.deploy.postCommand

  

Deploy post-command: Command to be executed after deployment.

team.deploy.common.deploy.preCommand

  

Deploy pre-command: Command to be executed prior to deployment.

team.deploy.common.isCompletePackage

true

false

 Deploy complete package: Specify true to deploy complete package.

team.deploy.common.load.ftp.hostname

  

Host name: FTP host name.

team.deploy.common.load.ftp.passwordFile

  

Password file: FTP password file.

team.deploy.common.load.ftp.userid

  

User ID: FTP user ID.

team.deploy.common.load.postCommand

  

Load post-command: Command to be executed after load.

team.deploy.common.load.preCommand

  

Load pre-command: Command to be executed prior to load.

team.deploy.common.loadMethod

Copy

ftp
Load method: Specify the type of load method to use and the appropriate command and/or FTP properties. When Copy is specified, the FTP host name, user ID, and password file attributes must not be specified. When ftp is specified, the FTP host name, user ID, and password file attributes are required. Valid values are:
Value Description
Copy Copy data sets on this system.
ftp FTP data sets from another system.

team.deploy.common.localPackageRoot.dir

  

Deployed package root directory:* Local package root directory.

team.deploy.common.packagedefinitionUUID

  

Package definition:* Specify the ID of the packaging build definition.

team.deploy.common.publishCumulativeDeploy

true

false

 Publish cumulative deploy manifest: Specify true to publish the cumulative deployment manifest file in the deployment result.

team.deploy.common.publishDeltaDeploy

true

false

 Publish delta deploy manifest: Specify true to publish the delta deployment manifest file in the deployment result.

team.deploy.common.publishRollbackManifest

true

false

 Publish rollback manifest: Specify true to publish the rollback manifest file in the deployment result.

team.deploy.common.remotePackageRoot.dir

  

Original package root directory:* Remote package root directory.

team.deploy.common.rollback.postCommand

  

Rollback post-command: Command to be executed after roll back.
team.deploy.common.rollback.preCommand  

Rollback pre-command: Command to be executed prior to roll back.

team.deploy.luw.runtimeRoot.dir

  

Runtime root directory: Specify a runtime root directory.
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.deploy.common.action
    • team.deploy.common.definition.version
    • team.deploy.common.filesystem
    • team.deploy.common.load.cd.deployment.useBuildAgentSettings
    • team.deploy.common.openSummaryWorkItem
    • team.deploy.common.restoreMappingPath
    • team.deploy.common.rollback.maximumKeep
    • team.deploy.common.rollback.multiRollbackCapable
    • team.deploy.ibmi.intermediateSaveFileLibrary
  • The following is a list of reserved properties names which can not be specified:
    • team.deploy.common.applicationDescription
    • team.deploy.common.applicationName
    • team.deploy.common.load.cd.localIp
    • team.deploy.common.load.cd.localPassword
    • team.deploy.common.load.cd.localPort
    • team.deploy.common.load.cd.localUserId
    • team.deploy.common.load.cd.nodeName
    • team.deploy.common.load.cd.packaging.useBuildAgentSettings
    • team.deploy.common.load.cd.remotePassword
    • team.deploy.common.load.cd.remoteUserId
    • team.deploy.common.packageLabel
    • team.deploy.common.restoreMappingList
    • team.deploy.common.rollback.multipleAllowed
    • team.deploy.common.version
    • team.deploy.ibmi.pfRestoreMethod
    • team.deploy.ibmi.pfRestoreUsrCmd
    • team.deploy.ibmi.savePfForRollback
    • team.deploy.zos.script
    • team.enterprise.ibmi.ASPName
    • team.enterprise.ibmi.setASP

teamBuildProperty Element - Unix Packaging Build

The following table describes the valid values for teamBuildProperty element attributes for a Unix Packaging build:

name value Description

team.package.common.applicationDescription

  

Description: Specify a description of the application.

team.package.common.applicationName

  

Name:* Specify the name of the application.

team.package.common.excludeFilePath

  

Exclude file: Specify the path to the exclude file to identify which built members to exclude.

team.package.common.isCompletePackage

true

false

 Complete package: Specify true if the package is a complete application.

team.package.common.isManifestPublished

true

false

 Publish manifest: Specify true to publish packaging manifest.

team.package.common.isPackagePublished

true

false

 Publish package: Specify true to publish packaging results.

team.package.common.packageRoot.dir

  

Package root directory:* Specify a directory on the build machine where you want to store all packages.

team.package.common.postPackageCommand

  

Package post-command: Specify a command to run on the build machine after packaging.

team.package.common.prePackageCommand

  

Package pre-command: Specify a command to run on the build machine before packaging.

team.package.common.shiplistFilePath

  

Ship list file:* Specify the path to the ship list file to identify which built members to package.

team.package.common.version

  

Version:* Specify the application version to package.

team.package.luw.buildRoot.dir

  

Build root directory:* Specify a build root directory.
Note:
  • The following is a list of reserved properties names which can not be specified unless overridden:
    • team.package.common.definition.version
    • team.package.common.filesystem
    • team.package.common.openSummaryWorkItem
    • team.package.common.packageBinariesSinceTimestamp
    • team.package.common.restoreMappingPath
    • team.package.common.shiplist.option
    • team.package.common.workitem.option
    • team.package.ibmi.intermediateSaveFileLibrary
    • team.package.ibmi.savefileOptions
    • team.package.zos.buildDefinition.uuid
    • team.package.zos.optional.shiplistFilePath
    • team.package.zos.script
  • The following is a list of reserved properties names which can not be specified:
    • team.enterprise.ibmi.ASPName
    • team.enterprise.ibmi.setASP
    • team.enterprise.packaging.deleteObsoleteOutputs
    • team.enterprise.packaging.includeImpactedObjects
    • team.enterprise.packaging.packagedWorkitems
    • team.package.common.buildDefinition.uuid
    • team.package.common.buildSnapshotId
    • team.package.common.exclude.binaries
    • team.package.common.include.binaries
    • team.package.common.isAutoClean
    • team.package.common.isConcurrentSafe
    • team.package.common.isIntermediatesPublished
    • team.package.common.timestamp.option
    • team.package.common.workItemPackaging
    • team.package.restore.mapping
    • team.package.ucd.component
    • team.package.ucd.generate
    • team.package.ucd.tk.script
    • team.package.ucd.type
    • team.package.ucd.versionName.convention
    • team.package.ucd.versionName.prefix