Plugin Information
This plugin enables slaves to auto-discover nearby Hudson master and join it automatically, thereby forming an ad-hoc cluster.
The primary use case of this came from "Hudson slave appliance" — a virtual machine pre-packaged with the swarm client CLI — that someone can just grab and run. With the swarm client, a person who's willing to contribute some of his computing power to the cluster just needs to run this virtual machine, and the cluster automatically gets additional resources. Because it's packaged as a VM, he need not worry about the builds/tests interfering with the host system or alter its settings unexpectedly. Usage
Available Options% java -jar swarm-client-jar-with-dependencies.jar -help
-description VAL : Description to be put on the slave
-executors N : Number of executors
-fsroot FILE : Directory where Hudson places files
-help (--help) : Show the help screen
-labels VAL : Whitespace-separated list of labels to be assigned for this
slave
-master VAL : Host name or IP address of the master. If this option is
specified, auto-discovery will be skipped
-name VAL : Name of the slave
FAQError configuration : "xxx.xxx.xxx.xxx doesn't have the URL configuration yet"This error indicates that the Hudson master running at the given URL has never configured, and therefore the swarm client cannot determine its HTTP URL. To fix this problem, please go to the system configuration screen of this Hudson, and click "submit". ChangelogVersion 1.3 (2010 Jan 14)
Version 1.1 (2009 Jul 15)
Version 1.0 (2009 May 23)
|

Comments (1)
Dec 18
Sarthak Dudhara says:
I am trying to connect to a hudson master using the swarm client. The problem i...I am trying to connect to a hudson master using the swarm client.
The problem is that it is first finding a currently non-existent hudson instance and tries to connect to it and gets a ConnectException. E.g. Machine A used to be a hudson master instance without any swarm plugin. I am trying to understand as to how does this slave know about the previously existing hudson instance?
Also, when i try to make it connect to a specific hudson 1.334 master on machine B, it still tries to connect to this zombie machine A. Do you think there is any caching on the client side? I tried to reboot the machine.
One more useful piece of info is that the same swarm client is able to connect to another hudson 1.334 swarm master hosted on machine C using auto discovery(without the -master option)
Any idea whats going on?