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

Graphs are empty (axis "undefined" labels) on job page

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      On my job pages, all warning-ng graphs are just empty (no data points, labels are all "undefined"). This seems to be a conflict with the dependency-check-plugin, which packages its own copies of eCharts and jQuery...

        Attachments

          Issue Links

            Activity

            tgr Tobias Gruetzmacher created issue -
            tgr Tobias Gruetzmacher made changes -
            Field Original Value New Value
            Component/s dependency-check-jenkins-plugin [ 18029 ]
            tgr Tobias Gruetzmacher made changes -
            Description On my job pages, all warning-ng graphs are just empty (no data points, labels are all "undefined"). I suspected the datamodel, since {{buildNumbers}} is empty on some, but the same data is rendered fine on the detail page... (Example for maven-warnings attached. This is the same from {{/getBuildTrend}} on the detail page and {{/getBuildTrendModel}} on the job page)

            The pipeline step for this is rather boring:

            {code:java}
            recordIssues sourceCodeEncoding: 'UTF-8', tools: [
                  checkStyle(reportEncoding: 'UTF-8'),
                  mavenConsole(reportEncoding: 'UTF-8'),
                  java(reportEncoding: 'UTF-8'),
                  javaDoc(reportEncoding: 'UTF-8'),
                ]
            {code}
            On my job pages, all warning-ng graphs are just empty (no data points, labels are all "undefined"). This seems to be a conflict with the {{dependency-check-plugin}}, which packages its own copies of eCharts and jQuery...
            Hide
            drulli Ulli Hafner added a comment -

            Steve Springett Plugins should never use and load JS libraries that are part of your plugin on a shared Jenkins page. This will produce conflicts on the composed page too easily. This might work for individual pages but not for pages shared by several plugins. Please use the corresponding API plugins that provide these JS libs on those pages. This has the additional benefit that you do not need to care about version upgrades or security fixes in the corresponding JS libraries.

            Please follow the guidelines in the corresponding blog article.

            Show
            drulli Ulli Hafner added a comment - Steve Springett Plugins should never use and load JS libraries that are part of your plugin on a shared Jenkins page. This will produce conflicts on the composed page too easily. This might work for individual pages but not for pages shared by several plugins. Please use the corresponding API plugins that provide these JS libs on those pages. This has the additional benefit that you do not need to care about version upgrades or security fixes in the corresponding JS libraries. Please follow the guidelines in the corresponding blog article .
            drulli Ulli Hafner made changes -
            Assignee Ulli Hafner [ drulli ] Steve Springett [ sspringett ]
            Show
            drulli Ulli Hafner added a comment - See https://github.com/jenkinsci/echarts-api-plugin
            drulli Ulli Hafner made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            drulli Ulli Hafner made changes -
            Link This issue relates to JENKINS-62633 [ JENKINS-62633 ]
            Hide
            drulli Ulli Hafner added a comment -

            I created a PR for the echarts API Plugin: https://github.com/jenkinsci/echarts-api-plugin/pull/64.

            This will at least fix the user problem of the empty charts. The general problem that the dependency-check plugin is not using the ECharts API Plugin is not resolved. So in future we may expect additional incompatibilities due to different ECharts versions.

            Show
            drulli Ulli Hafner added a comment - I created a PR for the echarts API Plugin: https://github.com/jenkinsci/echarts-api-plugin/pull/64 . This will at least fix the user problem of the empty charts. The general problem that the dependency-check plugin is not using the ECharts API Plugin is not resolved. So in future we may expect additional incompatibilities due to different ECharts versions.
            drulli Ulli Hafner made changes -
            Assignee Steve Springett [ sspringett ] Ulli Hafner [ drulli ]
            drulli Ulli Hafner made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            Hide
            drulli Ulli Hafner added a comment -

            This has been released quite some time ago.

            Show
            drulli Ulli Hafner added a comment - This has been released quite some time ago.
            drulli Ulli Hafner made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]

              People

              Assignee:
              drulli Ulli Hafner
              Reporter:
              tgr Tobias Gruetzmacher
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: