|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Code changed in jenkins
User: Akshay Dayal
Path:
pom.xml
src/main/java/hudson/remoting/Engine.java
src/main/java/hudson/remoting/engine/EngineUtil.java
src/main/java/hudson/remoting/engine/JnlpProtocol.java
src/main/java/hudson/remoting/engine/JnlpProtocol1.java
src/main/java/hudson/remoting/engine/JnlpProtocol2.java
src/main/java/hudson/remoting/engine/JnlpProtocolFactory.java
src/test/java/hudson/remoting/engine/EngineUtilTest.java
src/test/java/hudson/remoting/engine/JnlpProtocol1Test.java
src/test/java/hudson/remoting/engine/JnlpProtocol2Test.java
http://jenkins-ci.org/commit/remoting/90dd966a0c40c900dd58347fbfbc7958d8b40b65
Log:
JENKINS-26580 Refactor slave JNLP engine to make it easier to add more protocols in the future. The engine will now call a factory that returns a list of protocols to try in order. Developers can implement new protocols in separate classes and add them to the factory to be used. Added tests for existing protocols. I noticed the Engine class doesn't have a corresponding Test class. It would be nice to add one, but I think it needs more refactoring before it would be realistic to add tests for it.