Tolerate BindException in createWebServer#1175
Merged
Merged
Conversation
8 tasks
timja
approved these changes
May 28, 2026
jglick
added a commit
to jglick/kubernetes-plugin
that referenced
this pull request
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As of jenkinsci/kubernetes-plugin@07ad3c6 merged with jenkinsci/kubernetes-plugin@2153d3ce in jenkinsci/kubernetes-plugin#2837 sped up a bit with
mvnd test -Pktunnel -Dtest=KubernetesPipelineTest#runWithEnvVariablesInContext,KubernetesPipelineTest#runInPodWithLivenessProbefails both tests even though it is only the former that fails by timing out; the latter passes in isolation:
Normally the Jenkins server port is randomized so this is not an issue, but in this plugin due to the needs of the Kubernetes tunnel we fix a port and so it is important to handle the case that the prior server process is still shutting down and has not released the socket cleanly yet. With
-Djenkins-test-harness.version=999999-SNAPSHOTthe second test passes as expected:Note that this shows only
Jetty12EE9Provider. I guess #941 was just preparing for jenkinsci/jenkins#16714 but the effect onJetty12EE10Providercannot easily be tested yet.