Skip to content
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-19445, JENKINS-34213, JENKINS-34808, JENKINS-34121] Bump remoting to 2.59 #2357

Conversation

oleg-nenashev
Copy link
Member

This pull-request updates remoring in 1.651.x LTS baseline

Why upgrade instead of backporting:

  • All changes in 2.58 may be considered as bugs
  • Functional logic in JENKINS-19445, JENKINS-34808
  • 2.59 change is critical due to known issues in the JNLP3 protocol

Cons: the change has been released in jenkins-2.54 on May 15, so 2 weeks of soaking have not passed yet

Changes:

2.58:

2.59:

@olivergondza @aheritier @stephenc @reviewbybees

…oting to 2.59

Changes:

2.58:
* [JENKINS-34213](https://issues.jenkins-ci.org/browse/JENKINS-34213) - Ensure that the unexporter cleans up whatever it can each sweep (jenkinsci/remoting#81)
* [JENKINS-19445](https://issues.jenkins-ci.org/browse/JENKINS-19445) Force class load on UserRequest in order to prevent deadlock on windows nodes when using JNA and Subversion (jenkinsci/remoting#82)
* [JENKINS-34808](https://issues.jenkins-ci.org/browse/JENKINS-34808) - Allow user to adjust socket timeout (jenkinsci/remoting#68)

2.59:
* [JENKINS-34819](https://issues.jenkins-ci.org/browse/JENKINS-34819) - Allow disabling the remoting protocols individually. Works around issues like [JENKINS-34121](https://issues.jenkins-ci.org/browse/JENKINS-34121) (jenkinsci/remoting#83)
@oleg-nenashev
Copy link
Member Author

Off-topic: Seems @kohsuke released 1.651.2 from the parallel universe branch. I have no idea what I actually patch 😨

@ghost
Copy link

ghost commented May 17, 2016

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@aheritier
Copy link
Member

🐝 I'm +1000 to have these fix but less happy to have them bundled with the recent version which proposed JNLP3 protocol by default and which has some known issues :(
But I know that it is hard and cost a lost to create a maintenance branch of remoting which doesn't include JNPL3 :(

@oleg-nenashev
Copy link
Member Author

@aheritier 1.651.x LTS already uses the baseline with JNLP3 by default.
Good news is that it's possible to disable it via system properties with this fix

@stephenc
Copy link
Member

🐝

@olivergondza
Copy link
Member

👍

@aheritier
Copy link
Member

ok cool @oleg-nenashev thus 🐝 🐝 🐝

@oleg-nenashev
Copy link
Member Author

@reviewbybees done

@olivergondza
Copy link
Member

Cherrypicked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants