Branch: refs/heads/jnlp3 Home: https://github.com/jenkinsci/jenkins Commit: 9bb35a78b8298930adf978046e9f6c53c6853e27 https://github.com/jenkinsci/jenkins/commit/9bb35a78b8298930adf978046e9f6c53c6853e27 Author: Akshay Dayal <akshay_...@yahoo.com> Date: 2015-04-17 (Fri, 17 Apr 2015)
Changed paths: A core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java M core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java M pom.xml Log Message: ----------- [JENKINS-26580] Initial implementation of JNLP3-connect protocol Commit: e9f5caa13fa1a3d1bf602ec9d67dac75f3310889 https://github.com/jenkinsci/jenkins/commit/e9f5caa13fa1a3d1bf602ec9d67dac75f3310889 Author: Akshay Dayal <akshay_...@yahoo.com> Date: 2015-04-23 (Thu, 23 Apr 2015) Changed paths: M core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java Log Message: ----------- [JENKINS-26580] Updated implementation of Jnlp3 protocol Commit: 4915c31629afbc092345e600855279ce891e0dd4 https://github.com/jenkinsci/jenkins/commit/4915c31629afbc092345e600855279ce891e0dd4 Author: Kohsuke Kawaguchi <k...@kohsuke.org> Date: 2016-01-29 (Fri, 29 Jan 2016) Changed paths: M core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol.java M core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol3.java M core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java M pom.xml Log Message: ----------- Moved some of the server-side logic to remoting This way, the inner-working of the protocol can be kept private within the remoting module, which increases a modularity. Commit: a1d3634b0b1b6b20c075caf3b1ab73e5556acd62 https://github.com/jenkinsci/jenkins/commit/a1d3634b0b1b6b20c075caf3b1ab73e5556acd62 Author: Kohsuke Kawaguchi <k...@kohsuke.org> Date: 2016-02-02 (Tue, 02 Feb 2016) Changed paths: M core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java M core/src/main/java/jenkins/slaves/JnlpAgentReceiver.java M core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java M core/src/main/java/jenkins/slaves/JnlpSlaveHandshake.java Log Message: ----------- JnlpAgentReceiver needs to be adjusted for the new type Given that there's only one caller, I think handling AbstractMethodError is better than doing the compatibility method ping pong Compare: https://github.com/jenkinsci/jenkins/compare/9bb35a78b829^...a1d3634b0b1b -- You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.