Build Definition Reference

This section identifies the supported build types and their characteristics. The name, description, template ID, template aliases, and required build engine type are listed for each of the supported build types.

This section also describes the configuration elements and team build properties that are supported by each of the build types. Every build supports a predetermined set of configuration elements, the properties associated with those configuration elements, and team build properties. When creating a build, you must ensure to include only those configuration element properties and team build properties that are supported by the build.

When a build is created, all required configuration elements and team build properties are added to the build definition. The value for any configuration element property or team build property that you include will be used when the elements and properties are processed. Any configuration element property or team build property that you do not include will be set to its default value. The required configuration elements for each build type are identified in the ‘Configuration elements’ entry for the build type with an asterisk ^(*).

If you include a configuration element property for an optional configuration element, the optional configuration element will be added to the build and the specified property will be set to the specified value within that configuration element. Any other properties that are required by the optional configuration element which are not included will be defined using their default values. If you delete all configuration element properties for an optional configuration element, the element will be deleted from the build definition.

The following sections identify each of the supported build types and their details.

Ant Build

Ant Enterprise Extensions Build

Command Line Build

z/OS Deployment Build

z/OS Dependency Build

Rational Build Forge Build

Generic Build

Hudson/Jenkins Build

IBMi Command Line Build

IBMi Continuous Load Build

IBMi Deployment Build

IBMi Dependency Build

IBMi Packaging Build

IBMi Promotion Build

Microsoft Visual Studio Solution Build

Maven Build

z/OS Packaging Build

z/OS Promotion Build

Linux/UNIX Deployment Build

Linux/UNIX Packaging Build

z/OS Command Line Build

Build Engines

The following sections describe how to manage the build engines that support a build definition. Each section describes an element that can be specified within the createBuildDefinition or updateBuildDefinition element. These elements are not required and may not be applicable to the type of definition you are creating. Refer to the Build Reference section to determine which elements are valid for the build you are defining.

buildEngineDefine Element

Code one or more buildEngineDefine elements to specify the build engines that support the build definition. The following table describes the attributes for the buildEngineDefine element:

buildEngineDelete Element

Code one or more buildEngineDelete elements to specify the build engines that no longer support the build definition. These build engines will be removed from the build definition’s supporting build engine list. No error is generated if the build engine has already been removed from the build definitions supporting build engine list. The following table describes the attributes for the buildEngineDelete element:

Build Notifications

The following sections describe how to manage the notification process for the build definition. Each section describes an element that can be specified within the createBuildDefinition or updateBuildDefinition element. These elements are not required and may not be applicable to the type of definition you are creating. Refer to the Build Reference section to determine which elements are valid for the build you are defining.

buildNotification Element

Code one or more buildNotification elements to configure the notification process for the build definition. The following table describes the attributes for the buildNotification element:

Build Scheduling

The following sections describe how to manage the scheduling for automatic submission of the build definition. Each section describes an element that can be specified within the createBuildDefinition or updateBuildDefinition element. These elements are not required and may not be applicable to the type of definition you are creating. Refer to the Build Reference section to determine which elements are valid for the build you are defining.

buildSchedule Element

Code one or more buildSchedule elements to configure scheduling for the build definition using the Jazz scheduler. The following table describes the attributes for the buildSchedule element:

scheduleProperty Element

One or more scheduleProperty elements can be specified within a buildSchedule element to define build properties associated with the schedule item. For example:

<xt:buildSchedule hour="02" minute="30" mon="true">
  <xt:scheduleProperty
    name="monday"
    value="this is monday"
    description="Property for Monday"
    kind="com.ibm.team.build.property.string"
  />
</xt:buildSchedule>
    

The monday property will be available to the build when the schedule item submits the build. The following table describes the valid values for the scheduleProperty element attributes:

<xt:scheduleProperty name="name">value</xt:scheduleProperty>
            

teamBuildProperty Element

One or more teamBuildProperty elements can be specified within a buildSchedule element to define Team Build properties associated with the schedule item. For example:

<xt:buildSchedule hour="02" minute="30" mon="true">
  <xt:teamBuildProperty name="team.deploy.common.action" value="loadMain"/>
</xt:buildSchedule>
    

The team.deploy.common.action property will be available to the build when the schedule item submits the build. The following table describes the valid values for teamBuildProperty element attributes:

Build Properties

The following sections describe how to define general build properties used in a build definition. Each section describes an element that can be specified within the createBuildDefinition or updateBuildDefinition element. These elements are not required and may not be applicable to the type of definition you are creating. Refer to the Build Reference section to determine which elements are valid for the build you are defining.

buildProperty Element

Code as many buildProperty elements as are needed to define the custom build properties for the build definition. One buildProperty element is needed for each custom build property. The following table describes the valid values for the buildProperty element attributes:

<xt:buildProperty name="name">value</xt:buildProperty>
            

buildPropertyCopy Element

Code buildPropertyCopy elements to identify which properties are to be copied during a updateBuildDefinition task. When the updateBuildDefinition task propertyCopy attribute is set to true each property identified will have its value copied into the specified Ant property prior to any updates. The buildPropertyCopy facility can be used to save, update, and then restore build property values during a build.The following table describes the valid values for the buildPropertyCopy element attributes:

Configuration Properties

The following sections describe how to define the various configuration properties in a build definition. Each section describes a build definition sub-element that can be specified within the createBuildDefinition or updateBuildDefinition element. These sub-elements are used to define information required by a build configuration element. Each build definition sub-element represents a corresponding build configuration element. Not all configuration elements are applicable to a type of build. Refer to the Notes section of each build definition sub-element description to determine which configuration elements are valid for the build you are defining.

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

antBuildProperty Element

Code antBuildProperty elements to specify configuration details, the build file to use, and the build targets to be invoked for an Ant build. The antBuildProperty 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. The following table describes the valid values for the antBuildProperty element attributes:

antzBuildProperty Element

Code antzBuildProperty elements to specify configuration details, the build file to use, and the build targets to be invoked for an Ant with Enterprise Extensions build. The antzBuildProperty 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. The following table describes the valid values for the antzBuildProperty element attributes:

Notes

• The following is a list of reserved properties names which can not be specified unless overridden:
  • teamz.build.ant.buildAllItems
  • teamz.build.ant.conditionalBuild
• The following is a list of reserved properties names which can not be specified:
  • teamz.build.ant.buildableSubset

cmdBuildProperty Element

Code cmdBuildProperty elements to specify configuration details for the Command Line build. The cmdBuildProperty 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. The following table describes the valid values for the cmdBuildProperty element attributes:

dpndBuildProperty Element

Code dpndBuildProperty elements to specify configuration details, the build file to use, and the build targets to be invoked for a z/OS Dependency build. The dpndBuildProperty 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. The following table describes the valid values for the dpndBuildProperty element attributes:

Notes

• The following is a list of reserved properties names which can not be specified:
  • team.enterprise.build.buildmaps.needMigrateComponent

gwayBuildProperty Element

Code gwayBuildProperty elements to specify Enterprise Interactive Gateway configuration details for a z/OS Dependency build. The gwayBuildProperty element accepts two attributes, name and value, which are both required. The following table describes the valid values for the gwayBuildProperty element attributes:

hdsnBuildProperty Element

Code hdsnBuildProperty elements to specify the Hudson/Jenkins job to run. The hdsnBuildProperty element accepts two attributes, name and value, which are both required. The following table describes the valid values for the hdsnBuildProperty element attributes:

icmdBuildProperty Element

Code icmdBuildProperty elements to configure the required environment for the specified build command(s) and to specify the command to launch the build. Optionally, pre-build and post-build commands can be specified. The icmdBuildProperty 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. The following table describes the valid values for the icmdBuildProperty element attributes:

idpnBuildProperty Element

Code idpnBuildProperty elements to specify configuration details, the build file to use, and the build targets to be invoked for an IBMi Dependency build. The idpnBuildProperty 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. The following table describes the valid values for the idpnBuildProperty element attributes:

Notes

• The following is a list of reserved properties names which can not be specified unless overridden:
  • team.enterprise.build.buildmaps.needMigrateComponent
• The following is a list of reserved properties names which can not be specified:
  • team.enterprise.build.ant.createBuildMaps

iprmBuildProperty Element

Code iprmBuildProperty elements to specify configuration details, the build file to use, the build targets to be invoked, and the enterprise promotion configuration properties for an IBMi Promotion build. The iprmBuildProperty 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. The following table describes the valid values for the iprmBuildProperty element attributes:

Notes

• The following is a list of reserved properties names which can not be specified:
  • team.enterprise.promotion.sourceBuildResult

jdtBuildProperty Element

Code a jdtBuildProperty element to specify the location of an ECJ (Eclipse compiler for Java) log file, or directory of log files. The jdtBuildProperty 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. The following table describes the valid values for the jdtBuildProperty element attributes:

jntBuildProperty Element

Code a jntBuildProperty element to specify the location of a JUnit XML log file, or directory of log files. JUnit XML log files can be created by specifying a formatter type of "xml" when invoking JUnit. The jntBuildProperty 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. The following table describes the valid values for the jntBuildProperty element attributes:

msbBuildProperty Element

Code msbBuildProperty elements to specify the configuration for a Microsoft Visual Studio Solution build. The msbBuildProperty 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. The following table describes the valid values for the msbBuildProperty element attributes:

msbBuildItem Element

One or more msbBuildItem elements can be specified within an msbBuildProperty element to define a list of solution or project files to build. To define msbBuildItem elements, code an msbBuildProperty element with the name attribute set to com.ibm.team.build.msbuild.buildItem and include the msbBuildItem elements within. For example:

<xt:msbBuildProperty name="com.ibm.team.build.msbuild.buildItem">
  <xt:msbBuildItem .../>
</xt:msbBuildProperty>
    

The items will be built in the order given. At least one msbBuildItem element is required. The following table describes the valid values for the msbBuildProperty element attributes:

msbBuildText Element

The msbBuildText element can be specified within an msbBuildProperty element to define the value of a property in nested text format. For example:

<xt:msbBuildProperty name="com.ibm.team.build.msbuild.buildCmd">
  <xt:msbBuildText>Devenv</xt:msbBuildText>
</xt:msbBuildProperty>
    

Notes

• The following is a list of reserved properties names which can not be specified unless overridden:
  • com.ibm.team.build.msbuild.additionalArg
  • com.ibm.team.build.msbuild.buildOutput
  • com.ibm.team.build.msbuild.buildType
  • com.ibm.team.build.msbuild.buildConfiguration
  • com.ibm.team.build.msbuild.solutionFile
  • com.ibm.team.build.msbuild.workingDir

mstBuildProperty Element

Code mstBuildProperty elements to specify the configuration for MSTest unit tests. Unit tests will be run after a successful compilation. The mstBuildProperty element accepts two attributes, name and value, which are both required. The following table describes the valid values for the mstBuildProperty element attributes:

mvnBuildProperty Element

Code mvnBuildProperty elements to specify the path to the Maven project and the goals to build. The mvnBuildProperty element accepts two attributes, name and value, which are both required. The following table describes the valid values for the mvnBuildProperty element attributes:

nutBuildProperty Element

Code nutBuildProperty elements to specify the configuration for NUnit unit tests. Unit tests will be run after a successful compilation. The nutBuildProperty element accepts two attributes, name and value, which are both required. The following table describes the valid values for the nutBuildProperty element attributes:

prmtBuildProperty Element

Code prmtBuildProperty elements to specify configuration details, the build file to use, the build targets to be invoked, and the enterprise promotion configuration properties for an z/OS Promotion build. The prmtBuildProperty 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. The following table describes the valid values for the prmtBuildProperty element attributes:

Notes

• The following is a list of reserved properties names which can not be specified:
  • team.enterprise.promotion.sourceBuildResult

rbfBuildProperty Element

Code rbfBuildProperty elements to specify Build Forge configuration properties. The rbfBuildProperty element accepts two attributes, name and value, which are both required. The following table describes the valid values for the rbfBuildProperty element attributes:

Notes

• The following is a list of reserved properties names which can not be specified:
  • com.ibm.rational.connector.buildforge.project.uuid

ucdpBuildProperty Element

Code ucdpBuildProperty elements to specify the Post-build Deploy configuration. The ucdpBuildProperty 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. The following table describes the valid values for the ucdpBuildProperty element attributes:

Notes

The following is an example of using the nested text notation to specify "new line separated" items.

<ucdpBuildProperty name=team.udeploy.excludeFiles>file.name.01
file.name.03
</ucdpBuildProperty>
    

zcmdBuildProperty Element

Code zcmdBuildProperty elements to specify configuration details for the z/OS Command Line build. The zcmdBuildProperty 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. The following table describes the valid values for the zcmdBuildProperty element attributes:

zpreBuildProperty Element

Code zpreBuildProperty elements to specify configuration details for the z/OS Pre-Build Command. The zpreBuildProperty 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. The following table describes the valid values for the zpreBuildProperty element attributes:

zpstBuildProperty Element

Code zpstBuildProperty elements to specify configuration details for the z/OS Post-Build Command. The zpstBuildProperty 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. The following table describes the valid values for the zcmdBuildProperty element attributes:

Post-build Deliver Properties

The following sections describe how to define the Post-build Deliver properties used in a build definition. Each section describes an element that can be specified within the createBuildDefinition or updateBuildDefinition element. These elements are not required and may not be applicable to the type of definition you are creating. Refer to the Build Reference section to determine which elements are valid for the build you are defining.

All Post-build Deliver 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.

deliverProperty Element

Code deliverProperty elements to specify the trigger policy used to determine when to automatically deliver component changes, the target stream you would like to flow changes to, the components that will be delivered, and the owner of the snapshot created (ownership can only be changed if all components are delivered) for the Post-build Delivery facility. The deliverProperty 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. The following table describes the valid values for the deliverProperty element attributes:

Team Build Properties

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 the Build Reference section 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.

teamBuildProperty Element - Ant Enterprise Extensions Build

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

teamBuildProperty Element - z/OS Deployment Build

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

From: DATA.SET.FROM0
To:   DATA.SET.TO0

From: DATA.SET.FROM1
To:   DATA.SET.TO1
            

DATA.SET.FROM0;DATA.SET.TO0;DATA.SET.FROM1;DATA.SET.TO1
            

Notes

• 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 Element - z/OS Dependency Build

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

Notes

• 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

teamBuildProperty Element - Enterprise Interactive Gateway

The following table describes the valid values for teamBuildProperty element attributes for a Enterprise Interactive Gateway session:

Notes

• The following is a list of reserved properties names which can not be specified:
  • team.enterprise.gateway.ispzxenv
  • team.enterprise.gateway.ping

teamBuildProperty Element - IBMi Deployment Build

The following table describes the valid values for teamBuildProperty element attributes for an IBMi Deployment build:

From: libraryf0
To:   libraryt0

From: libraryf1
To:   libraryt1
            

ibraryf0;;libraryt0;;libraryf1;;libraryt1
            

Notes

• 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 - IBMi Dependency Build

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

Notes

• 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

teamBuildProperty Element - IBMi Packaging Build

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

LIB.NAME(*) OBJTYPE(*)
LIB.NAME(*) OBJTYPE(abc)
LIB.NAME(def) OBJTYPE(*)
            

LIB.NAME(abc) OBJTYPE(def)
            

LIB.NAME(*) OBJTYPE(*)
LIB.NAME(*) OBJTYPE(abc)
LIB.NAME(def) OBJTYPE(*)
            

LIB.NAME(abc) OBJTYPE(def)
            

fromLib,toLib,fromLib2,toLib2
            

Notes

• 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.exclude.hfs.binaries
  • team.package.common.include.hfs.binaries
  • 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 - IBMi Promotion Build

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

Notes

• The following is a list of reserved properties names which can not be specified unless overridden:
  • team.promotion.filesystem

teamBuildProperty Element - Ant Enterprise Extensions Publishing

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

teamBuildProperty Element - z/OS Packaging Build

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

DATA.SET.NAME(*)
            

DATA.SET.NAME(MEMBER)
            

directory:pattern
            

myOtherProject/:**/*.jar:myJavaProject:**/*.jar:
            

DATA.SET.NAME(*)
            

DATA.SET.NAME(MEMBER)
            

directory:pattern
            

myOtherProject/:**/*.jar:myJavaProject:**/*.jar:
            

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

Notes

• 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:

Notes

• 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:

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:

/ComponentName/ProjectFolder/RulesFolder/RulesFile.loadrules
            

/ComponentName/RulesFile.loadrules
            

Notes

• 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:

/ComponentName/ProjectFolder/RulesFolder/RulesFile.loadrules
            

/ComponentName/RulesFile.loadrules
            

Notes

• 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 IBMi Command Line Build

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

Notes

• 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 IBMi Continuous Load Build

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

Notes

• 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 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:

Notes

• 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:

Notes

• 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:

Notes

• 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:

Notes

• 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.exclude.hfs.binaries
  • team.package.common.include.binaries
  • team.package.common.include.hfs.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