The task is used to publish cached build maps for an Enterprise Extensions Dependency Build that uses the Post Compile Exit. During a normal build, build maps are published after each file is compiled. The Post Compile exit changes this behavior to allow for customized processing, such as extended validation after a compile, by caching the build maps locally on the build engine. Once the exit has completed it signals back to the Dependency Build to proceed with publishing which is performed by this task.
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 |
| buildResultUUID |
The UUID of the build result. The value of this attribute is typically ${buildResultUUID} because the property is built-in when using the Jazz Build Engine. This attribute is used to identify the cached build maps for this build.
|
Yes |
| errors | A semicolon-separated list of file versionable UUIDs that are in error and that should not have their build maps published. | No |
| publish |
Specifies whether or not to publish build maps. Specify false if the compiles were unsuccessful and none of the build maps are to be published or true if the compiles were successful and all of the build maps are to be published. If this property is not set, it will default to false and build maps will not be published.
In the case where publishing should occur only for successful compiles, specify |
No |
Publish cached build map results:
<antz:publishBuildMap
buildResultUUID="${buildResultUUID}"
errors="${team.enterprise.build.ant.postCompileReturn}"
passwordFile="${passwordFile}"
publish="${team.enterprise.build.ant.postCompilePublish}"
repositoryAddress="${repositoryAddress}"
userId="${userId}"/>