[JIRA] [remoting] (JENKINS-33886) Can only connect one JNLP3 slave per IP address
Title: Message Title akshay_abd edited a comment on JENKINS-33886 Re: Can only connect one JNLP3 slave per IP address I tried 2 different simple setups today and could not reproduce the issue:* 3 JNLP nodes connect to the master from the same machine* 2 JNLP nodes connect to the master from different machinesIn both cases the nodes were able to stay connected and do work. [~jeffkayser] - you mentioned in GitHub that your setup involved a proxy - could you tell me some details so I can mirror your setup? https://github.com/jenkinsci/jenkins/commit/e9f5caa13fa1a3d1bf602ec9d67dac75f3310889 Also - if you have time can you confirm that a "simple" setup - ie. nodes connecting without a proxy involved work? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-33886) Can only connect one JNLP3 slave per IP address
Title: Message Title akshay_abd commented on JENKINS-33886 Re: Can only connect one JNLP3 slave per IP address I tried 2 different simple setups today and could not reproduce the issue: 3 JNLP nodes connect to the master from the same machine 2 JNLP nodes connect to the master from different machines In both cases the nodes were able to stay connected and do work. Jeff Kayser - you mentioned in GitHub that your setup involved a proxy - could you tell me some details so I can mirror your setup? https://github.com/jenkinsci/jenkins/commit/e9f5caa13fa1a3d1bf602ec9d67dac75f3310889 Also - if you have time can you confirm that a "simple" setup - ie. nodes connecting without a proxy involved work? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
Title: Message Title akshay_abd resolved as Fixed Jesse Glick feel free to verify if needed. Jenkins / JENKINS-26759 FileSystemJarCache not defensive enough Change By: akshay_abd Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
akshay_abd commented on JENKINS-26759 FileSystemJarCache not defensive enough k - if it is a case of a corrupt file we can at least verify the checksum as you mentioned. I've opened https://github.com/jenkinsci/remoting/pull/44 for review that does this. 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.
[JIRA] [remoting] (JENKINS-27216) "remoting.Channel" can not garbage collect
akshay_abd commented on JENKINS-27216 "remoting.Channel" can not garbage collect Could you provide some details on how to reproduce this issue? Did this happen over time as slaves connected & disconnected? Or did this happen over time with the same set of slaves connected? Also what kind of slaves are being used? SSH, JNLP? 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.
[JIRA] [remoting] (JENKINS-28127) The Jenkins master should not re-calculate jar hashes each time a slave connects
akshay_abd started work on JENKINS-28127 The Jenkins master should not re-calculate jar hashes each time a slave connects Change By: akshay_abd (28/Apr/15 8:42 AM) Status: Open In Progress 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.
[JIRA] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
akshay_abd started work on JENKINS-26759 FileSystemJarCache not defensive enough Change By: akshay_abd (28/Apr/15 8:42 AM) Status: Open In Progress 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.
[JIRA] [remoting] (JENKINS-28127) The Jenkins master should not re-calculate jar hashes each time a slave connects
akshay_abd created JENKINS-28127 The Jenkins master should not re-calculate jar hashes each time a slave connects Issue Type: Improvement Assignee: akshay_abd Components: remoting Created: 28/Apr/15 8:37 AM Description: Each time a slave connects to the master there is an interaction where jars are transferred to the slave if needed. This is done by looking at the slave's jar cache and comparing the hashes against the master's jars. The master does not have a shared cache, so it is has to re-calculate the hashes for every slave it deals with. This is done even when no jars need to be transferred (ie. the slave jar cache is already up-to-date). If there are a lot of ephemeral slaves that come and go then this becomes wasteful for the master. Ideally the master's cache should be a singleton that can be accessed for interactions with any slave. There is even a TODO in the JarLoaderImpl that talks about this. Project: Jenkins Priority: Minor Reporter: akshay_abd 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.
[JIRA] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
akshay_abd assigned JENKINS-26759 to akshay_abd FileSystemJarCache not defensive enough Change By: akshay_abd (28/Apr/15 8:38 AM) Assignee: akshay_abd 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.
[JIRA] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
akshay_abd commented on JENKINS-26759 FileSystemJarCache not defensive enough We're still on JDK 6 right? So we can't use Files.move - correct? We can at least verify the checksums. 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.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted I've created a pull request on the remoting repo that adds JNLP3: https://github.com/jenkinsci/remoting/pull/41 I'm still writing tests for the changes to jenkins-core, I'll create a pull request for that soon too. It would be nice to get a few security folks to review these changes. Also in a follow-up CL I'll be enabling JNLP3, probably through a flag, getting folks to try it and help with end-to-end testing would be appreciated. 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.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd started work on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: akshay_abd (24/Jan/15 3:09 PM) Status: Open In Progress 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.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Added a pull request to the remoting project: https://github.com/jenkinsci/remoting/pull/28 This is a refactor-only pull request. It should make it easier for developers to add support for more protocols in the slave. 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.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd created JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Issue Type: Improvement Assignee: akshay_abd Components: core Created: 23/Jan/15 7:45 PM Description: For more details about the requirements and possible implementation refer to: https://groups.google.com/forum/#!topic/jenkinsci-dev/Q1KMOSE1IEc Project: Jenkins Priority: Minor Reporter: akshay_abd 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.
