Build System 2.0 - ArtifactFilePublisher task
We use Jazz 2.0 Build System (Win32) currently in our team. The build output should be a zip file with published process description (basically HTML files). For process publishing we use EPF Composer command publishing. I used Exec Ant task to launch EPFC. Publishing works well, Zip Ant task works also fine. But when the ArtifactFilePublisher task is called, I receive an authentication exception.
Unable to update last contact time for engine: com.ibm.team.repository.transport.client.AuthenticationException: CRJAZ0124I Invalid username or password.
Could you give me an advice, please?
Thank you.
Unable to update last contact time for engine: com.ibm.team.repository.transport.client.AuthenticationException: CRJAZ0124I Invalid username or password.
Could you give me an advice, please?
Thank you.
13 answers
Hi Michele,
Most of the Build Ant tasks update the last contact time of the engine as a side effect of their main work.
Please check the process area (team area or project area) that owns the build definition for the build in question, then see if the permissions for that process area, or any of its parent team areas, have been overridden the overall permissions at project level.
For example, if the process area nesting is:
Project A
..Team Area B
....Team Area C
and the build definition is associated with C, the permission lookup happens in the order: C, B, A. So you need to check all of these.
Another thing you should check is the user id used in the Ant tasks, which may differ from the user id used for JBE, and therefore may have different permissions (unless you've granted Build permissions to the Everyone role).
Most of the Build Ant tasks update the last contact time of the engine as a side effect of their main work.
Please check the process area (team area or project area) that owns the build definition for the build in question, then see if the permissions for that process area, or any of its parent team areas, have been overridden the overall permissions at project level.
For example, if the process area nesting is:
Project A
..Team Area B
....Team Area C
and the build definition is associated with C, the permission lookup happens in the order: C, B, A. So you need to check all of these.
Another thing you should check is the user id used in the Ant tasks, which may differ from the user id used for JBE, and therefore may have different permissions (unless you've granted Build permissions to the Everyone role).
Hi Michele,
Most of the Build Ant tasks update the last contact time of the engine as a side effect of their main work.
Please check the process area (team area or project area) that owns the build definition for the build in question, then see if the permissions for that process area, or any of its parent team areas, have been overridden the overall permissions at project level.
For example, if the process area nesting is:
Project A
..Team Area B
....Team Area C
and the build definition is associated with C, the permission lookup happens in the order: C, B, A. So you need to check all of these.
Another thing you should check is the user id used in the Ant tasks, which may differ from the user id used for JBE, and therefore may have different permissions (unless you've granted Build permissions to the Everyone role).
page 2of 1 pagesof 2 pages