teamAccept

The teamAccept task accepts change sets into the given repository workspace. Change sets are accepted from all its incoming flow targets. Optionally, the task can create a snapshot after the changes have been accepted.

The following table contains teamAccept task attributes.

Attribute	Description	Required
repositoryAddress	Address of the team repository to use. The value of this attribute is typically ${repositoryAddress} because that property is built-in when using the Jazz™ Build Engine.	Yes
userId	User ID for authentication to the repository. Requires password or passwordFile to be set.	Yes
workspaceName	For the teamAccept task, the name of the workspace to accept changes into.	Note: Either workspaceUUID or workspaceName must be given, but not both.
workspaceUUID	For the teamAccept task, the UUID of the workspace to accept changes into. If you have multiple workspaces with the same name, you might need to use this attribute instead of workspaceName.	Note: Either workspaceUUID or workspaceName must be given, but not both.
certificateFile	The path to the file that contains the user's login certificate for authentication. Requires password or passwordFile to be set. You can specify certificateFile or repositoriesFile, but not both.	No
buildResultUUID	For the teamAccept task, the build result to publish the snapshot to. This enables the build workspace to be re-created at a later time from the build result. If this attribute is provided, then snapshotName must also be provided. At most, set this attribute for one invocation of this task per build. Build results cannot have more than one snapshot associated with them. This task throws an exception if the build result already has a snapshot associated with it.	No
changeSetFile	The path that is relative to the base directory of the build file, or the full path to a file where serialized change sets are stored. The format of the file is one UUID per line. The file lists the workspace UUID where the changes were accepted followed by the UUIDs of the change sets that were accepted. The file can be consumed by the workItemPublisher task when its inputFileType is CHANGESET.	No
changesAcceptedProperty	The Ant property in which to store the number of changes that are accepted. The property is set only if at least one change is accepted.	No
customIteration	The Ant attribute for specifying a custom iteration that will be associated to the build snapshot. This is expected to take the following form: `parentTimeline/parentIteration1/parentIteration2/customIteration`. The timeline and iteration segments are the `identifier` (which is unique) and not the `display name`. The timeline is also expected to be from the same project area that contains the build definition. If we are not specifying a custom iteration Ant property, then the behavior is that we will navigate from the build result to the build definition, then the owning process area, and select the current iteration. The iteration that is associated to the build snapshot is made visible in the history graph for a component. For more information, see Viewing component history graphically.	No
failOnError	If true (the default), the task fails if it encounters an error. If false, some errors are ignored and the task is completed.	No
integratedWindows	Whether to use Integrated Windows Authentication	No
kerberos	Whether to use Windows user credentials using Kerberos/SPNeGO.	No
password	Password for the user ID for authentication to the repository. Either password or passwordFile can be provided, but not both.	No
passwordFile	The password file to use for authentication to the connection. You can create a suitable password file by invoking the Jazz Build Engine with the -createPasswordFile argument. You can only specify one password file. Either password or passwordFile can be provided, but not both.	No
repositoriesFile	The repositories registry file containing a listing of repositories and their login credentials. You can specify repositoriesFile or certificateFile, but not both. If you specify repositoriesFile, do not specify either password or passwordFile. The repositories file is created and updated through the use of scm login and logout commands.	No
reuseLoginOption	The first time an Ant task logs in to a repository, a connection is not terminated at the end of this task. All subsequent tasks reuse this connection as long as they connect to same repository with same user ID. When a task logs in to a different repository or with a different user ID, the previous connection is terminated and a new connection is created and reused.	No
smartCard	Whether to use the connected smart card for authentication (true or false). Requires userId to be set. For more information about smart card authentication, see Connecting to repositories and project areas.	No
snapshotName	The name of a snapshot to create from the workspace, after the change sets have been accepted. If this attribute is provided, then buildResultUUID must also be provided. If provided, the build result is updated with the build snapshot information. This enables the build workspace to be re-created at a later time from the build result. At most, set this attribute for one invocation of this task per build. Build results cannot have more than one snapshot associated with them. This task throws an exception if the build result already has a snapshot associated with it.	No
snapshotUUIDProperty	The Ant property in which to store the UUID of the snapshot. Do not set if no snapshot is created.	No
verbose	Specifies more message output. The default is false.	No

Example

<teamAccept repositoryAddress="${repositoryAddress}"
		            userId="${userId}"
		            password="${password}"
		            workspaceName="workspace1"
		            buildResultUUID="${buildResultUUID}"
		            snapshotName="test"
		            verbose="true" />

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki