Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-73939] Un-inline JavaScript in chart-setup.jelly #358

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

yaroslavafenkin
Copy link
Contributor

JENKINS-73939

Testing done

Tested against warnings-ng's PMD and CheckStyle.

https://www.loom.com/share/b6ee2a0732ce43e2af21ed5a6718a4ff?sid=1339b3bf-4076-4f88-91be-b5f22e316314

https://www.loom.com/share/ac5e2d4439374506b76ad9a8e85bac69?sid=6e1ca5df-dfc8-44c2-9f22-27c984be634d

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

Copy link

codecov bot commented Oct 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.42%. Comparing base (d542ca5) to head (672c83e).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #358   +/-   ##
=========================================
  Coverage     51.42%   51.42%           
  Complexity       17       17           
=========================================
  Files             7        7           
  Lines           105      105           
  Branches          3        3           
=========================================
  Hits             54       54           
  Misses           51       51           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@uhafner uhafner added the internal Internal changes without user or API impact label Oct 16, 2024
Copy link
Member

@uhafner uhafner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I installed the PR locally and the trend configuration button still works as expected. (Example configure button is in https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/main/178/maven-warnings/)

@uhafner uhafner merged commit 43d2089 into jenkinsci:main Oct 16, 2024
30 of 31 checks passed
@nfalco79
Copy link
Member

The version 5.5.1-2 that include this change cause the trend graph in build page a infinite loading loader
The error in console is:

Uncaught TypeError: ajaxProxy.getConfigurableBuildTrendModel is not a function
    renderAsynchronously http://localhost:8090/jenkins/static/afdc740e/plugin/echarts-api/js/echarts-api.js:479
    renderConfigurableTrendChart http://localhost:8090/jenkins/static/afdc740e/plugin/echarts-api/js/echarts-api.js:519
    <anonymous> http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:10
    <anonymous> http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:4
    EventListener.handleEvent* http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:1
echarts-api.js:479:23

https://issues.jenkins.io/browse/JENKINS-74775?filter=23848

@yaroslavafenkin
Copy link
Contributor Author

The version 5.5.1-2 that include this change cause the trend graph in build page a infinite loading loader The error in console is:

Uncaught TypeError: ajaxProxy.getConfigurableBuildTrendModel is not a function
    renderAsynchronously http://localhost:8090/jenkins/static/afdc740e/plugin/echarts-api/js/echarts-api.js:479
    renderConfigurableTrendChart http://localhost:8090/jenkins/static/afdc740e/plugin/echarts-api/js/echarts-api.js:519
    <anonymous> http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:10
    <anonymous> http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:4
    EventListener.handleEvent* http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:1
echarts-api.js:479:23

https://issues.jenkins.io/browse/JENKINS-74775?filter=23848

@nfalco79 you've assigned yourself to the JIRA ticket, does that imply you're working on the fix?

@nfalco79
Copy link
Member

The issue in 5.5.1-3 version

@nfalco79
Copy link
Member

The version 5.5.1-2 that include this change cause the trend graph in build page a infinite loading loader The error in console is:

Uncaught TypeError: ajaxProxy.getConfigurableBuildTrendModel is not a function
    renderAsynchronously http://localhost:8090/jenkins/static/afdc740e/plugin/echarts-api/js/echarts-api.js:479
    renderConfigurableTrendChart http://localhost:8090/jenkins/static/afdc740e/plugin/echarts-api/js/echarts-api.js:519
    <anonymous> http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:10
    <anonymous> http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:4
    EventListener.handleEvent* http://localhost:8090/jenkins/adjuncts/afdc740e/io/jenkins/plugins/echarts/render-configurable-trend-chart.js:1
echarts-api.js:479:23

https://issues.jenkins.io/browse/JENKINS-74775?filter=23848

@nfalco79 you've assigned yourself to the JIRA ticket, does that imply you're working on the fix?

No, I was investigating, the reported suggestion didn't work, so I was here to report the problem.

@yaroslavafenkin
Copy link
Contributor Author

Looking at the stack trace it's rather caused by #357

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Internal changes without user or API impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants