Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73636

Use correct icon when ID is overwritten

XMLWordPrintable

      Hi,

      we have a pipeline that is triggering a build and publishes issues with multiple, different JDKs. Currently we're defining different IDs in the publishIssues call with adding a postfix, e.g. for the build with JDK17 we use ID=checkstyle-jdk17 and for the build with JDK21 we use ID=checkstyle-jdk21. In these cases the Icons are not picked up in the overview.

      Is it possible to change the behaviour and check for the id prefix to show the correct icon?

      Thanks in advance!

      Best regards
      Norman

        1. image-2024-10-29-17-15-07-569.png
          image-2024-10-29-17-15-07-569.png
          11 kB

          [JENKINS-73636] Use correct icon when ID is overwritten

          Norman created issue -
          Ulli Hafner made changes -
          Link New: This issue is duplicated by JENKINS-72777 [ JENKINS-72777 ]
          Ulli Hafner made changes -
          Summary Original: Support publishing issues multiple times for one report format New: Aut
          Ulli Hafner made changes -
          Summary Original: Aut New: Use correct icon wh
          Ulli Hafner made changes -
          Summary Original: Use correct icon wh New: Use correct icon when ID is overwritten
          Ulli Hafner made changes -
          Labels New: help-wanted
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]

          Ulli Hafner added a comment -

          As mentioned in JENKINS-72777 a new persistent property needs to be added to the results that stores the actual parser ID that has been used.

          Ulli Hafner added a comment - As mentioned in JENKINS-72777 a new persistent property needs to be added to the results that stores the actual parser ID that has been used.
          Manuel made changes -
          Attachment New: image-2024-10-29-17-15-07-569.png [ 63478 ]

          Manuel added a comment -

          I found a similar issue: When using a custom ID for a tool used by an aggregating recordIssues step, for example

          recordIssues( 
            id: "build-x64-linux",
            name: "build (x64-linux)",
            aggregatingResults: 'true',
            tools: [
               [ $class: 'io.jenkins.plugins.analysis.warnings.Cmake', id: 'configure-x64-linux', pattern: 'build-x64-linux.log' ],
               [ $class: 'QtTranslation', pattern: 'build-x64-linux.log' ]
            ]
          )

          the overview on the build page doesn't use the correct name of the analyzer, and instead displays a generic "Static Analysis", for example

          Should I create a dedicated issue for this problem or will this automatically be fixed when this issue is fixed?

          Manuel added a comment - I found a similar issue: When using a custom ID for a tool used by an aggregating recordIssues step, for example recordIssues(    id: "build-x64-linux",   name: "build (x64-linux)",   aggregatingResults: 'true',   tools: [      [ $class: 'io.jenkins.plugins.analysis.warnings.Cmake', id: 'configure-x64-linux', pattern: 'build-x64-linux.log' ],      [ $class: 'QtTranslation', pattern: 'build-x64-linux.log' ]   ] ) the overview on the build page doesn't use the correct name of the analyzer, and instead displays a generic "Static Analysis", for example Should I create a dedicated issue for this problem or will this automatically be fixed when this issue is fixed?

            drulli Ulli Hafner
            nbrass Norman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: