Add Japanese l10N files.

git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@9233 71c3de6d-444a-0410-be80-ed276b4c234a

war/resources/help/system-config/master-slave/clock_ja.html

+<div><!-- TODO 誰か訳して -->
+  Many aspects of a build are sensitive to the clock, and therefore if the clock of the machine
+  that Hudson runs and that of the slave differ significantly, it can cause mysterious problems.
+  Consider synchronizing clocks between machines by NTP.
+</div>

war/resources/help/system-config/master-slave/command_ja.html

+<div><!-- TODO 誰か訳して -->
+  Command to be used to launch a slave agent program, which controls the slave
+  computer and communicates with the master.
+
+  <h3>JNLP slave agents</h3>
+  <p>
+  Leave this field empty if you'd like to launch slave agents via JNLP.
+  With this setting, the slave information page (hudson/computer/***/) will
+  have a JNLP launch icon, and you can click that link from the correct slave
+  machine to launch a slave agent via JNLP.
+  <p>
+  This mode is convenient for Windows slaves that often do not have a remote execution
+  mechanism.
+
+  <h3>ssh/rsh slave agents</h3>
+  <p>
+  When an actual command is specified in this field,
+  this command is executed on the
+  master, and Hudson assumes that the executed program launches the <tt>slave.jar</tt>
+  program on the correct slave machine.
+
+
+  <p>
+  A copy of <tt>slave.jar</tt> can be found in <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>

war/resources/help/system-config/master-slave/description_ja.html

+<div><!-- TODO 誰か訳して -->
+  Optional human-readable description of this slave. This information
+  is displayed on the project configuration screen.
+
+  <p>
+  When you have slaves that are different from others, it's often helpful
+  to use this field to explain what is different. For example, entering
+  "Windows slave" in this field would allow project owners to choose to
+  always build on a Windows machine (for example, if they need some
+  Windows-specific build tool.)
+</div>
\ No newline at end of file

war/resources/help/system-config/master-slave/jnlpSecurity_ja.html

+<div><!-- TODO 誰か訳して -->
+    Controls how Hudson permits launching via JNLP.
+
+    <dl>
+        <dt><b>
+            Launch only from Computer detail. Require Login if security enabled.
+        </b></dt>
+        <dd>
+            <em>This is the default and normal setting.</em>
+            In this mode, Hudson provides the JNLP launch link on the computer view.
+            If Security is enabled, then the link will only be available to authenticated users.
+        </dd>
+
+        <dt><b>
+            Launch from front page. Require Login if security enabled.
+        </b></dt>
+        <dd>
+            In this mode, Hudson provides the JNLP launch link on both the computer view and the Build Executor Status
+            sidepanel.
+            If Security is enabled, then the link will only be available to authenticated users.
+        </dd>
+
+        <dt><b>
+            Launch only from Computer detail. Login never required.
+        </b></dt>
+        <dd>
+            In this mode, Hudson provides the JNLP launch link on the computer view.
+            The link will always be available whenever the slave is offline.
+            <br />
+            <b>WARNING!</b> In this mode security is disabled.  Thus slaves can be started by <em>anyone
+            that can access this server</em>.  Slaves have the ability to execute arbitrary code on the
+            master.  <b>Do not select this option unless you are fully aware of the risks</b>
+        </dd>
+
+        <!--dt><b>
+            Launch from front page. Login never required.
+        </b></dt>
+        <dd>
+            In this mode, Hudson provides the JNLP launch link on both the computer view and the Build Executor Status
+            sidepanel.
+            The link will always be available whenever the slave is offline.
+        </dd-->
+
+    </dl>
+</div>
\ No newline at end of file

war/resources/help/system-config/master-slave/label_ja.html

+<div><!-- TODO 誰か訳して -->
+  Labels (AKA tags) are used for grouping multiple slaves into one logical group.
+
+  <p>
+  For example, if you have multiple Windows slaves and you have jobs that require
+  Windows, then you can configure all your Windows slaves to have the label 'windows',
+  then tie the job to the 'windows' label. This allows your job to run on any
+  of your Windows slaves but not on anywhere else.
+</div>
\ No newline at end of file

war/resources/help/system-config/master-slave/name_ja.html

+<div>
+  このHudsonのスレーブをユニークに識別する名前です。
+
+  <p>
+  この値はどんな文字でも使用できます。また、スレーブのホスト名と同じにする必要はありませんが、
+  多くの場合同じにした方が便利です。
+</div>
\ No newline at end of file

war/resources/help/system-config/master-slave/numExecutors_ja.html

+<div><!-- TODO 誰か訳して -->
+  This controls the number of concurrent builds that Hudson can perform on this slave.
+  So the value affects the overall system load Hudson may incur.
+  A good value to start with would be the number of processors.
+
+  <p>
+  Increasing this value beyond that would cause each build to take longer, but it could increase
+  the overall throughput, because it allows CPU to build one project while another build is waiting
+  for I/O.
+
+  <p>
+  Setting this value to 0 is useful to remove a disabled slave from Hudson temporarily without
+  losing other configuration information.
+</div>
\ No newline at end of file

war/resources/help/system-config/master-slave/remoteFS_ja.html

+<div><!-- TODO 誰か訳して -->
+  <p>
+  A slave needs to have a directory dedicated to Hudson. Specify
+  the absolute path of this work directory on the slave, such as
+  '/export/home/hudson'.
+
+  <p>
+  Slaves do not maintain important data (other than active workspaces
+  of projects last built on it), so you can possibly set the slave
+  workspace to a temporary directory. The only downside of doing this
+  is that you may lose the up-to-date workspace if the slave is turned off.
+</div>

war/resources/help/system-config/master-slave/slave-agent-port_ja.html

+<div>
+  HudsonはTCPポートを使用して、JNLPで起動したスレーブエージェントと通信を行います。
+  通常このポートは衝突を避けるためにランダムに選ばれますが、システムをセキュアにするのが難しくなります。
+  JNLPを使用しないなら、このTCPポートをなしにすることをおすすめします。
+  もしくは、ファイアーウォールを設定できるように、このポート番号を固定にすることもできます。
+</div>
\ No newline at end of file

war/resources/help/system-config/master-slave/usage_ja.html

+<div><!-- TODO 誰か訳して -->
+  Controls how Hudson schedules builds on this machine.
+
+  <dl>
+    <dt><b>
+      Utilize this slave as much as possible
+    </b></dt>
+    <dd>
+      This is the default and normal setting.
+      In this mode, Hudson uses this slave freely. Whenever there is a build
+      that can be done by using this slave, Hudson will use it.
+    </dd>
+
+    <dt><b>
+      Leave this machine for tied jobs only
+    </b></dt>
+    <dd>
+      In this mode, Hudson will only build a project on this machine when
+      that project specifically has this slave as the "assigned node".
+
+      This allows a slave to be reserved for certain kinds of jobs.
+      For example, to run performance tests continuously from Hudson,
+      you can use this setting with # of executors as 1, so that only one performance
+      test runs at any given time, and that one executor won't be blocked
+      by other builds that can be done on other slaves.
+    </dd>
+  </dl>
+</div>
\ No newline at end of file