[JENKINS-52204] - Skip port availability check when -tunnel option is set #279
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.
This is a fix for the JENKINS-52204 regression in Remoting 3.22 and Jenkins 2.129. When
-tunnel
option is set, Jenkins may be connecting to different host. So it does not make much sense to verify port availability in that case.The issue comes from #275 . Although I believe that the current
-tunnel
behavior is rather obsolete and should be reworked/removed (JENKINS-52246), I propose to just disable the check and restore compatibility for nowCC @denami @jeffret-b @dwnusbaum