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
Upgrade jQuery to 3.5.x #4929
Upgrade jQuery to 3.5.x #4929
Conversation
- Remove uses of the .size() and .load() methods - Remove the unit tests on the maven test command because they have not been ported
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.
Taking this one out of WIP status as the proper work is done but there are some discussions and some work left.
Most of the JS unit tests do not work with this PR. These tests are very difficult to migrate and offer little value, as most of the use-cases they cover are also covered by JTH and ATH suites. Any thoughts on this?
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.
are you running ATH over this? (more than just the default smoke tests that run on CI)
Most of the JS unit tests do not work with this PR. These tests are very difficult to migrate and offer little value, as most of the use-cases they cover are also covered by JTH and ATH suites. Any thoughts on this?
Can probably remove.
I'll get back to you with a full ATH run hopefully tomorrow |
I have verified that there are no ATH errors that don't happen in other PRs. |
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.
Random manual testing (like monkey typing on keyboards), looking for console errors. Core (without plugins) was working fine, testing with multiple pages.
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.
Nice! This PR makes my jQuery plugin obsolete (if this PR is part of an LTS). Is jQuery 3.x then available as $
in views or do we still need workarounds? (How does this change relate to https://github.com/jenkinsci/jquery-plugin? Is this plugin then obsolete as well?)
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.
Just ran some manual smoke tests, clicking random stuff and checking both behavior and the inspect console, as Wadeck did; and everything looks good to me.
It is not. Plugins are still needed for their intended use case. The jQuery version in core is contained to the bundles generated by webpack and not exposed to the |
For context, |
I have run a comprehensive PCT suite and have found some errors that I need to go through. I suspect is due to outdated POMs but still, I'd like to have the PR marked as on hold maybe after the LTS selection. |
@fqueiruga should unhold be removed now? |
TBH I would like to give it a few weeklies of margin, maybe get it in 2.266 or 2.267. The reason is that I don't want the bug reports arising from tables-to-divs to be muddied by this PR, if that makes sense. |
thoughts on shipping in 2.266? |
I've mentioned that this change is coming in a proposed blog post inviting users and administrators to assist with testing Jenkins weekly releases. I think that including it in Jenkins 2.266 does not complicate bug triage any more than it is already. |
Let's go then! |
This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback. Thanks! |
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.
It is a bit YOLO, but we should merge it sooner or later. I vote for merging sooner, we have only 1 month before the Christmas break so extra week is a good addition for user feedback
I think this is a break change? My plugin stopped working. |
@liuweiGL can you comment this on the issue? From what I see, your plugin is no loading jQuery in package.json, or in POM.xml. This change was also scoped to just Jenkinsci and should have no sideffects on other plugins. From what I see, that $ variable may be referring to the prototypejs instance that Jenkins provides. jQuery does not provide a |
@liuweiGL I think your plugin may have broken on the tables-to-divs release on Jenkins 2.264, given that the change is to DOM transversal on a form function. You could report the issue on the appropiate epic https://issues.jenkins.io/browse/JENKINS-62437 and tag the issue with the label |
Thank you very much. |
This PR bumps the jQuery version from 2.1.4 to 3.5.x.
I have created the PR in order to properly test it with a CI build.
JS changes:
Testing command:
docker run --rm -it -p 8080:8080 -e ID=4929 jenkins/core-pr-tester
Proposed changelog entries
Proposed upgrade guidelines
N/A
Submitter checklist
Proposed changelog entries
section only if there are breaking changes or other changes which may require extra steps from users during the upgradeDesired reviewers
@uhafner
@Wadeck
@timja
Maintainer checklist
Before the changes are marked as
ready-for-merge
:Proposed changelog entries
are correctupgrade-guide-needed
label is set and there is aProposed upgrade guidelines
section in the PR title. (example)lts-candidate
to be considered (see query).