-
Bug
-
Resolution: Not A Defect
-
Critical
-
None
-
. Dimension 14.3
. Dimension Plugin 0.8.13
. Jenkins 1.642
Hi,
I am struggling with error thrown from dimension plug-in, which shows like this.
[DIMENSIONS] SUCCESS: Using Current Project '005:12011302_SRC_PRJ'. [DIMENSIONS] Using 'D:\ctip_repo\ci\jobs\GSCM_GET_NETWORK\workspace\' as the Project work area. [DIMENSIONS] Scanning repository: 0.91 sec [DIMENSIONS] Scanning local work area: 0.00 sec [DIMENSIONS] Getting files: 0.00 sec [DIMENSIONS] Getting Project: 1.45 sec [DIMENSIONS] Operation completed [DIMENSIONS] Operation completed [DIMENSIONS] ) [DIMENSIONS] Calculating change set for directory 'gscm-webapp-network'... FATAL: Unable to run change set callout - PCC2110013E You do not have the role to browse the document detailed description
I don't know where this came from.
These are my environment for using jenkins-dimension.
Please help me.
. Dimension 14.3
. Dimension Plugin 0.8.13
. Jenkins 1.642
The user account that the Jenkins Dimensions Plugin is using to connect to Dimensions CM most likely does not have permission to fetch the detailed description of a request from Dimensions CM. However, the Jenkins Dimensions Plugin code that generates the build's change log in Jenkins tries to fetch the related requests' Titles, IDs and Detailed Descriptions. I may revisit this as we only really use the Title and ID in the change log.
So, if you are connecting to Dimensions CM with a user account named "jenkinsbuild" (for example), then you need to give that account the ability to browse requests (depending on versions of the server and client libraries, you may also need to give that account the ability to update a request's detailed description).
These privileges are Product > Request > Browse in Admin Console (REQUEST_BROWSE from command-line) or Product > Request > Add/Update Detailed Description in Admin Console (REQUEST_DETAILDESC from command-line). The best way of assigning this privilege is likely to be to add the "jenkinsbuild" (for example) account to a group or role, rather than directly assigning the privilege, but this will depend on your process model.