[JIRA] [swarm-plugin] (JENKINS-28518) Slaves not discovering when Maven is not enabled on the master
Title: Message Title Joshua Knarr commented on JENKINS-28518 Re: Slaves not discovering when Maven is not enabled on the master Bumping for me. I am using puppet to install jenkins and was pulling my hair out. Loading the configuration and clicking "save" once fixes this. 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] [swarm-plugin] (JENKINS-28518) Slaves not discovering when Maven is not enabled on the master
Title: Message Title Jörg Ziegler commented on JENKINS-28518 Re: Slaves not discovering when Maven is not enabled on the master Seeing the same error message with 1.642.2 running on Linux, using swarm-client-2.0-jar-with-dependencies.jar. It seems to be a missing initialization: The jenkins-url is correctly populated after jenkins installations but apparently not returned to the swarm client. Going to /configure and manually saving the configuration once fixes the problem. It's not a blocker since there's an easy workaround, however since we're trying to auto-setup jenkins from docker, it's a bummer that we can't fully automate it. Hoping that with this info it'll be an easy fix? 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] [swarm-plugin] (JENKINS-28518) Slaves not discovering when Maven is not enabled on the master
Title: Message Title Peter Jnsson commented on JENKINS-28518 Re: Slaves not discovering when Maven is not enabled on the master That is quite weird. I would have to take a look at this case. 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] [swarm-plugin] (JENKINS-28518) Slaves not discovering when Maven is not enabled on the master
Title: Message Title Srini Sundaram created an issue Jenkins / JENKINS-28518 Slaves not discovering when Maven is not enabled on the master Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 21/May/15 10:47 AM Environment: OS - Centos 6.5 64 bit Jenkins - 1.614 Swarm - 1.24 Slave - swarm-client-1.24-jar-with-dependencies.jar Java (Master Slave) - OpenJDK Runtime Environment (build 1.8.0_45-b13) Labels: jenkins plugin slave Priority: Minor Reporter: Srini Sundaram Hi, This is not a blocker. I was trying the slave auto discovery in the above mentioned scenario. Without having the Maven installed on the master when I tried: java -jar swarm-client-1.24-jar-with-dependencies.jar -autoDiscoveryAddress 192.168.55.22 -name Slave1
