• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Critical Critical
    • dimensionsscm-plugin
    • 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

          [JENKINS-48645] Dimension plug-in error

          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.

          David Conneely added a comment - 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.

          See comments

          David Conneely added a comment - See comments

          jay jang added a comment -

          dconneely

          I really appreciated your comment. I could figure it out.

          btw this function was newly added on the plugin ? I did not face this error with the past version of plugin.

          ( 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.)

          jay jang added a comment - dconneely I really appreciated your comment. I could figure it out. btw this function was newly added on the plugin ? I did not face this error with the past version of plugin. ( 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.)

          David Conneely added a comment - - edited

          wkdjj Great - glad to hear you fixed things! For whether this is new behaviour: It depends what version of the plugin you were using before you upgraded to 0.8.13. It's not something that's changed recently AFAIK, but it could be something that changed some time ago (say before 0.8.8). If you updated the version of the Dimensions CM server, it could be due to that too. I will look into changing the Plugin anyway . - Cheers, David.

          David Conneely added a comment - - edited wkdjj  Great - glad to hear you fixed things! For whether this is new behaviour: It depends what version of the plugin you were using before you upgraded to 0.8.13. It's not something that's changed recently AFAIK, but it could be something that changed some time ago (say before 0.8.8). If you updated the version of the Dimensions CM server, it could be due to that too. I will look into changing the Plugin anyway . - Cheers, David.

          jay jang added a comment -

          dconneely Thanks

          the previous version of plug-in we were using is 0.8.2

          Does this version also include the function ??

          Thanks

          jay jang added a comment - dconneely Thanks the previous version of plug-in we were using is 0.8.2 Does this version also include the function ?? Thanks

          Yes. On more examination of the plugin's source code history (I only took ownership of the plugin around version 0.8.8), it looks like the Jenkins Dimensions Plugin code has always queried the request's detailed description since version 0.6.0 (when the enhancement to show the related requests was implemented). I'm planning on doing a new release in the next few weeks (before end January), I'll try to include a fix in that release (the temporary workaround until then is to give the "jenkinsbuild" account - the account that you use with the Jenkins Dimensions Plugin - the privilege to update detailed descriptions).

          David Conneely added a comment - Yes. On more examination of the plugin's source code history (I only took ownership of the plugin around version 0.8.8), it looks like the Jenkins Dimensions Plugin code has always queried the request's detailed description since version 0.6.0 (when the enhancement to show the related requests was implemented). I'm planning on doing a new release in the next few weeks (before end January), I'll try to include a fix in that release (the temporary workaround until then is to give the "jenkinsbuild" account - the account that you use with the Jenkins Dimensions Plugin - the privilege to update detailed descriptions).

          Code changed in jenkins
          User: David Conneely
          Path:
          src/main/java/hudson/plugins/dimensionsscm/DimensionsAPI.java
          http://jenkins-ci.org/commit/dimensionsscm-plugin/278998a778e0e789c811228383feed9fc25b2f38
          Log:
          [FIX JENKINS-48645] No need to ask for request detailed description.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: David Conneely Path: src/main/java/hudson/plugins/dimensionsscm/DimensionsAPI.java http://jenkins-ci.org/commit/dimensionsscm-plugin/278998a778e0e789c811228383feed9fc25b2f38 Log: [FIX JENKINS-48645] No need to ask for request detailed description.

          Release 0.8.14 should resolve this issue.

          David Conneely added a comment - Release 0.8.14 should resolve this issue.

            Unassigned Unassigned
            wkdjj jay jang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: