-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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-35190] Do not invoke PingFailureAnalyzer for agent=>master ping failures #2377
[JENKINS-35190] Do not invoke PingFailureAnalyzer for agent=>master ping failures #2377
Conversation
🐝 |
/** Keep in a separate method so we do not even try to do class loading on {@link PingFailureAnalyzer} from an agent JVM. */ | ||
private void analyze(Throwable cause) throws IOException { | ||
for (PingFailureAnalyzer pfa : PingFailureAnalyzer.all()) { | ||
pfa.onPingFailure(channel,cause); |
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.
If you modify this code, please add handling of Runtime Exceptions
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 would be nice, though (a) there are no implementations to test, as noted in the description, (b) I spent some time testing the patch as written and would have to spend more time retesting with any other modifications.
🐝 with a comment related to the legacy code |
We also have +1 from Oliver, so I'm going to merge it . #2341 will be integrated manually since it makes sense in any case |
… on the agent side. (jenkinsci#2377)
Related to jenkinsci/remoting#85.
@reviewbybees