-
Notifications
You must be signed in to change notification settings - Fork 54
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
Bump versions of JS UI plugins to latest version #571
Conversation
Replacements: - Bootstrap4 -> replaced by Boostrap5 (5.0.1-2) - Popper -> replaced by Popper2 (2.5.4-2) Version upgrade: - Echarts -> 5.1.2-2 Plugin new in BOM: - Datatables -> 1.10.25-1
I don't think we can add this till we remove 2.235 which we could probably do? Any plugins added need to be available on all lines |
junit depends on bootstrap4 and ehcharts. Now we have something with both bootstrap 4 and 5 in the mix (seems like a recepie for disaster) junit PCT (hudson.tasks.junit.JUnitResultArchiverTest.basic) fails with:
|
I created a PR for the JUnit plugin 2 months ago: jenkinsci/junit-plugin#272 |
Depends on jenkinsci/junit-plugin#342. |
@ufhaner Not sure I agree with that assessment. While that would certainly fix the problem, I don't think we are necessarily blocked on it. The problem seems to me that |
@uhafner I came up with a more clear argument:
In other words, jenkinsci/junit-plugin#342 being unfinished necessitates keeping Commit de25291083107967a29e5fd9ca3933fbea0c0990de25291 in jenkinsci/echarts-api-plugin#228 is based on top of echarts-api 5.0.2-1. It updates the build toolchain. I am asking that we backport these build toolchain updates to the 5.0.2 line and release 5.0.2-2. This would allow us to update the 5.0.2 version of echarts-api in the BOM, even without jenkinsci/junit-plugin#342, and unblock my other BOM work in the short term. For instructions on how to do a backport, see: https://gist.github.com/jglick/86a30894446ed38f918050c1180483e2 |
Replacements:
Version upgrade:
Plugin new in BOM: