mirror of
https://github.com/jenkinsci/jenkins.git
synced 2026-11-18 06:22:29 +00:00
git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@1523 71c3de6d-444a-0410-be80-ed276b4c234a
38 lines
1.3 KiB
HTML
38 lines
1.3 KiB
HTML
<div>
|
|
Command to be used to launch a slave agent program, which controls the slave
|
|
computer and communicates with the master. This command is executed on the
|
|
master, and Hudson assumes that the executed program launches <tt>slave.jar</tt>
|
|
program on the correct slave machine.
|
|
|
|
<p>
|
|
A copy of <tt>slave.jar</tt> can be found on <tt>WEB-INF/slave.jar</tt> inside
|
|
<tt>hudson.war</tt>.
|
|
|
|
<p>
|
|
In a simple case, this could be
|
|
something like "ssh <i>hostname</i> java -jar ~/bin/slave.jar".
|
|
|
|
However, it is often a good idea to write a small shell script like the following on a slave,
|
|
so that you can control the location of Java and/or slave.jar, as well as set up any
|
|
environment variables specific to this slave node, such as PATH.
|
|
|
|
<pre>
|
|
#!/bin/sh
|
|
exec java -jar ~/bin/slave.jar
|
|
</pre>
|
|
|
|
<p>
|
|
You can use any command to run a process on the slave machine, such as RSH,
|
|
as long as stdin/stdout of this process will be connected to
|
|
"java -jar ~/bin/slave.jar" eventually.
|
|
|
|
<p>
|
|
In a larger deployment, It is also worth considering to load <tt>slave.jar</tt> from
|
|
a NFS-mounted common location, so that you don't have to update this file every time
|
|
you update Hudson.
|
|
|
|
<p>
|
|
Setting this to "ssh -v <i>hostname</i>" may be useful for debugging connectivity
|
|
issue.
|
|
</div>
|