-
Notifications
You must be signed in to change notification settings - Fork 21
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
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. |
There was a problem hiding this 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/)
The version 5.5.1-2 that include this change cause the trend graph in build page a infinite loading loader
|
@nfalco79 you've assigned yourself to the JIRA ticket, does that imply you're working on the fix? |
The issue in 5.5.1-3 version |
No, I was investigating, the reported suggestion didn't work, so I was here to report the problem. |
Looking at the stack trace it's rather caused by #357 |
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