• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • Jenkins 2.462.3
      ECharts API Plugin Version 5.5.1-3
      OWASP Dependency-Check Plugin Version 5.5.1
      JUnit Plugin Version 1307.vdd5b_2646279e
      Warnings Plugin Version 11.10.0
    • v5.5.1-4

      I don't know the root cause, it appears like it might be connected to related CSP efforts. Maybe just needs to be updated with some of the open dependabot PRs first? idk

      Browser console shows

      Uncaught TypeError: ajaxProxy.getConfigurableBuildTrendModel is not a function

      which appears to be coming from
      static/.../plugin/echarts-api/js/echarts-api.js
      adjuncts/.../io/jenkins/plugins/echarts/render-configurable-trend-chart.js

          [JENKINS-74775] Trend not loading for dependency-check

          Zac Thompson added a comment -

          If my plugins page is to be believed, the previous versions I had (when it worked) were these:
          ECharts API Plugin Version 5.5.1-1
          JUnit Plugin Version 1302.va_b_878c32eb_b_5
          Warnings Plugin Version 11.9.0

          Zac Thompson added a comment - If my plugins page is to be believed, the previous versions I had (when it worked) were these: ECharts API Plugin Version 5.5.1-1 JUnit Plugin Version 1302.va_b_878c32eb_b_5 Warnings Plugin Version 11.9.0

          Nikolas Falco added a comment - - edited

          I had update pom plugin and BOM version that include 5.5.1-3 but the trend chart is broken. I see the PR in EChart repository but I didn't see changes in the documentation on "how to use trend graph"

          CC drulli

          Nikolas Falco added a comment - - edited I had update pom plugin and BOM version that include 5.5.1-3 but the trend chart is broken. I see the PR in EChart repository but I didn't see changes in the documentation on "how to use trend graph" CC drulli

          Yaroslav Afenkin added a comment - - edited

          Hi zthompson,

          Do you mind providing a minimal reproducible example, so I can have a look at what's going on locally? Also please specify what browser you are using.

          Yaroslav Afenkin added a comment - - edited Hi zthompson , Do you mind providing a minimal reproducible example, so I can have a look at what's going on locally? Also please specify what browser you are using.

          Nikolas Falco added a comment - - edited

          I had reproduced in our production instance with:

          • jenkins 2.462.3
          • latest dependency check plugin
          • echart-api-plugin version 5.5.1-3

          Create a freestyle project
          Configure a publisher

            <publishers>
              <org.jenkinsci.plugins.DependencyCheck.DependencyCheckPublisher plugin="dependency-check-jenkins-plugin@5.4.7">
                <failedTotalCritical>0</failedTotalCritical>
                <failedTotalHigh>0</failedTotalHigh>
                <totalThresholdAnalysisExploitable>false</totalThresholdAnalysisExploitable>
                <newThresholdAnalysisExploitable>false</newThresholdAnalysisExploitable>
                <pattern>**/*.xml</pattern>
                <stopBuild>false</stopBuild>
              </org.jenkinsci.plugins.DependencyCheck.DependencyCheckPublisher>
            </publishers>
          

          Put these dependency-check-report-one-vulnerability.xml dependency-check-report-ten-vulnerabilities.xml report files report in the workspace folder and run a couple of build to produce a trend chart

          I use Firefox latest version

          Nikolas Falco added a comment - - edited I had reproduced in our production instance with: jenkins 2.462.3 latest dependency check plugin echart-api-plugin version 5.5.1-3 Create a freestyle project Configure a publisher <publishers> <org.jenkinsci.plugins.DependencyCheck.DependencyCheckPublisher plugin= "dependency-check-jenkins-plugin@5.4.7" > <failedTotalCritical> 0 </failedTotalCritical> <failedTotalHigh> 0 </failedTotalHigh> <totalThresholdAnalysisExploitable> false </totalThresholdAnalysisExploitable> <newThresholdAnalysisExploitable> false </newThresholdAnalysisExploitable> <pattern> **/*.xml </pattern> <stopBuild> false </stopBuild> </org.jenkinsci.plugins.DependencyCheck.DependencyCheckPublisher> </publishers> Put these dependency-check-report-one-vulnerability.xml dependency-check-report-ten-vulnerabilities.xml report files report in the workspace folder and run a couple of build to produce a trend chart I use Firefox latest version

          Thanks a lot for the reproductions steps. I've found what causes the issue, I'll file a PR with the fix shortly.

          Yaroslav Afenkin added a comment - Thanks a lot for the reproductions steps. I've found what causes the issue, I'll file a PR with the fix shortly.

          Here's the PR with the fix: https://github.com/jenkinsci/echarts-api-plugin/pull/360

          Feedback is welcome.

          Yaroslav Afenkin added a comment - Here's the PR with the fix: https://github.com/jenkinsci/echarts-api-plugin/pull/360 Feedback is welcome.

          Yaroslav Afenkin added a comment - Released as https://github.com/jenkinsci/echarts-api-plugin/releases/tag/v5.5.1-4

            yafenkin Yaroslav Afenkin
            zthompson Zac Thompson
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: