The task is used to create all the files necessary to run an Enterprise Extensions (EE) Dependency Build based on the change sets attached to the specified work items.

Attributes

The task supports Team Build Attributes, Build Extensions Debugging Attributes, Build Extensions General Attributes, as well as, its own task specific attributes. Click on a link for more information on the common attributes.

The following table describes the task specific attributes for the task:

Task Specific Attributes
Attribute Description Required
buildFile Specifies the name of the buildable files XML file. This is typically buildableFiles.xml, the default name when using the Dependency Build. Yes
buildFolder Specifies the path to the buildable files XML file. This is typically the value of the fetchDestination attribute. Yes
buildLoadFile Specifies the name of the file agent operation list XML file. This is typically FAOperationList.xml, the default name when using the Dependency Build. Yes
buildLoadFolder Specifies the path to the file agent operation list XML file. This is typically the value of the fetchDestination attribute. Yes
buildPrefix Specifies the prefix for z/OS data names. If not specified, this attribute will default to the value of the ${team.enterprise.scm.resourcePrefix} property because it is built-in when using the Dependency Build. Yes
buildResultUUID Specify the UUID of the build result to use to identify the change sets to package. The value of this attribute is typically ${buildResultUUID} because the property is built-in when using the Jazz Build Engine. For more information on the methods for identifying the change sets to use for identifying buildable files, refer to the Identifying Change Sets section. Yes
checkContent Specify true to check each identified part for a content change. Only parts with a content change will be included in the resulting buildable files XML file. Specify false to include all parts in the buildable files XML file regardless of a change in content. The default is false. No
createFolders Specifies whether or not component roots will be loaded as directories in the file system. Valid values are true or false. The default is false. No
exclude

Specify a comma-separated list of component names in the form: componentName, or a comma-separated list of component names with a list of comma-separated project names in the form: componentName(projectName). For example: 

exclude="com.ibm.ims.core.db"
exclude="com.ibm.ims.core.db,com.ibm.ims.core.tm"
exclude="com.ibm.ims.core.db(com.ibm.ims.core.db.base)"
exclude="com.ibm.ims.core.db(com.ibm.ims.core.db.base),
com.ibm.ims.core.tm(com.ibm.ims.core.tm.appc,com.ibm.ims.core.tm.base)"

When exclude is specified, parts from the identified components or component projects will be excluded from the resulting buildable files XML file. If exclude is not specified, all parts will be included in the resulting buildable files XML file. If a component project list is specified, only parts from the specified projects will be excluded; component parts from projects not specified in the list will be included in the resulting buildable files XML file.

No4
fetchDestination Local directory where the fetched files are to be stored. The default value of this attribute is ${team.enterprise.scm.fetchDestination} because that property is built-in when using the Dependency Build. Yes
fetchWorkspace Specifies whether or not to fetch the build workspace. Valid values are true or false. The default is true. No
include

Specify a comma-separated list of component names in the form: componentName, or a comma-separated list of component names with a list of comma-separated project names in the form: componentName(projectName). For example: 

include="com.ibm.ims.core.db"
include="com.ibm.ims.core.db,com.ibm.ims.core.tm"
include="com.ibm.ims.core.db(com.ibm.ims.core.db.base)"
include="com.ibm.ims.core.db(com.ibm.ims.core.db.base),
com.ibm.ims.core.tm(com.ibm.ims.core.tm.appc,com.ibm.ims.core.tm.base)"

When include is specified, only parts from the identified components or component projects will be included in the resulting buildable files XML file. If include is not specified, all parts will be included in the resulting buildable files XML file.

No4
linkWorkItems Specifies whether or not to link the build result to the work items associated with the build. Valid values are true or false. The default is false. No
personalBuild Specify true to treat this build as a personal build. Specify false to treat this build as a team build. The default is the value of the Ant property personalBuild. This attribute is used to override the default personalBuild value. No
processAreaName Specify the name of the process area that contains the Enterprise Extensions system definitions. Yes
reportCondensed This option controls the format of build report. Valid values are: true and false. If true, a streamlined version of the build report will be generated. If false, the full build report, including all file item data, will be generated. The default is false. No
reportFile Specify the name of the resulting report file. No
reportFolder Specify the full path on the build machine where the report file is to be written. If the folder is not found, it will be created. A relative path from the build’s base directory may be specified. When reportFile is set, this attribute is required. No1
workItemId Specifies the ID of a work item with linked change sets that are to be built. No4
workItemIds Specifies a comma-separated list of work item IDs with linked change sets that are to be built.. No4
workItemProperty Name of the Ant property in which to return the comma-separated work item IDs associated with the build. No
workItemReportFile Specify the name of the resulting work item report file. No
workItemReportFolder Specify the full path on the build machine where the report file is to be written. If the folder is not found, it will be created. A relative path from the build’s base directory may be specified. When the workItemReportFile attribute is set, this attribute is required. No2
workItemReportHtmlFile Specify the name of the resulting work item HTML report file. No
workItemReportHtmlFolder Specify the full path on the build machine where the report file is to be written. If the folder is not found, it will be created. A relative path from the build’s base directory may be specified. When the workItemReportHtmlFile attribute is set, this attribute is required. No3
workItemReportHtmlTitle Specify the title for the resulting work item HTML report file. When the workItemReportHtmlFile attribute is set, this attribute is required. No3
workspaceUUID Specify the UUID of the workspace which contains the components to be packaged. The value of this attribute is typically ${team.scm.workspaceUUID} because the property is built-in when using the Jazz Build Engine. Yes
1 When reportFile is set, this attribute is required.
2 When workItemReportFile is set, this attribute is required.
3 When workItemReportHtmlFile is set, this attribute is required.
4 Either workItemId or workItemIds needs to be specified to identify the work item/work items to build.

Notes

Examples

Create build files to build the "com.ibm.ims.core.tm.appc" project: 

<xt:createBuildFilesForComponents
    repositoryAddress="${repositoryAddress}"
    userId="${userId}"
    passwordFile="${passwordFile}"
    buildFile="buildableFiles.xml"
    buildFolder="${dir.work}"
    buildLoadFile="FAOperationList.xml"
    buildLoadFolder="${dir.work}"
    buildResultUUID="${buildResultUUID}"
    checkContent="${checkContent}"
    linkWorkItems="true"
    processAreaName="${buildProjectArea}"
    reportCondensed="true"
    reportFile="buildableReport.txt"
    reportFolder="${dir.work}"
    workItem="556142"
    workItemReportFile="workitemReport.txt"
    workItemReportFolder="${dir.work}"
    workItemReportHtmlFile="${htmlReportFileName}"
    workItemReportHtmlFolder="${dir.work}"
    workspaceUUID="${team.enterprise.scm.workspaceUUID}"
/>