[JIRA] (JENKINS-16835) jenkins.war version 1.500: windows slave connection issue
Kevin Dyer commented on JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Note "Install as service" option does not upgrade slave.jar. If you delete the service and slave.jar and then reinstall as a service it works. http://stackoverflow.com/questions/9177223/jenkins-service-fail-to-start-on-windows-2008/15629182#15629182 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/groups/opt_out.
[JIRA] (JENKINS-16835) jenkins.war version 1.500: windows slave connection issue
hagay goldstein commented on JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Hi, Got the same issue when upgrading to 1.500 WIN slave service doesn't work. Whenever the machine reboots I need to upload the task because the service is malfunction. Regards, Hagay 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/groups/opt_out.
[JIRA] (JENKINS-16835) jenkins.war version 1.500: windows slave connection issue
Linards L commented on JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Comment above should be added to FAQ ! 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/groups/opt_out.
[JIRA] (JENKINS-16835) jenkins.war version 1.500: windows slave connection issue
Josh Sinfield commented on JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Hi Alben, I recently upgraded from 1.491 to 1.504 and it caused issues with communication to the slave. in 1.498 there was a security update for encrypting configuration data etc. : https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 This means you have to re-key all your configuration files (see your Manage Jenkins page of your installation). I also had to replace the slave.jar, and add the "-secret xxx " option to the jenkins-slave.xml configuration on the slave ( where is the secret token). These can both be obtained from the manage nodes configuration page. After restarting the Node and Master they both connected together OK. Cheers, Josh 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/groups/opt_out.
[JIRA] (JENKINS-16835) jenkins.war version 1.500: windows slave connection issue
alben shao created JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 16/Feb/13 3:42 AM Description: After upgrade to jenkins 1.500 or 1.501, jenkins can't connect to windows slave (run as windows service) with error "access denied", even after I re-install/restart "jenkins slave" service. Then I downgrade to jenkins 1.472(the version I previously used), it works well. Is it a bug/issue of jenkins 1.500? Note that, all jenkins version can work well if the slave run as web start. Thanks/Alben Due Date: 16/Feb/13 12:00 AM Environment: win7 as jenkins slave Project: Jenkins Priority: Critical Reporter: alben shao 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/groups/opt_out.
