-
Notifications
You must be signed in to change notification settings - Fork 150
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
Plugin loading page recursively and eventually crashing browser #339
Comments
I just uninstalled all disabled plugins and confirmed problem still occurs. Environment details above have been updated to reflect this. |
+1 |
Any solution yet? The problem still exists :) |
@ftakanashi you have the same problem? I haven't found a solution yet, but I'm curious what similarities/differences our environments have |
My environment is something like this:
(Actually, my instance is deployed via official jenkins docker image of 2.346.1 and I updated the .war file to 2.426.3 And plugins with versions:
Update: disable publish-over-ssh (which is 1.24 now) -> restart Jenkins -> update it to 1.25 -> restart Jenkins -> enable it |
@ftakanashi, I just saw your update. I'll be trying that tomorrow. Thanks for the tip! Edit, just pulled the trigger and it works!! Thank you so much for the suggestion. I didn't even see the update in the list before now |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux (Ubuntu 18.04 LTS). All running on a single host.
Reproduction steps
Expected Results
Page doesn't load recursively
Actual Results
Any job using the Publish-Over-SSH plugin will recursively load the current page inside the "validation-error-area" div for the "Source Files" field of each "Transfer Set".
Anything else?
We're well-aware that several of our plugins are terribly out of date, and several others are deprecated or otherwise no longer supported. Unfortunately, we don't have a great path forward on that short of moving off of jenkins entirely, which would be a much larger effort.
We did not run any plugin or system updates immediately prior to this issue occurring, nor did we change any job configuration. Given the wide-spread nature of this issue (any job using the plugin), we believe it to be unrelated to the job configuration at all.
I saw nothing that appeared relevant in the jenkins system logs, but the browser console does show several warnings including one that seems to be looking for jquery (
$ is not a function
)Jobs continue to run perfectly fine, but we're simply unable to change their configuration.
Are you interested in contributing a fix?
I'm open to it, but wouldn't know where to start.
The text was updated successfully, but these errors were encountered: