[Qa-jenkins-scm] [jenkins.debian.net] 03/03: doc: the old way to start agent came back at some point, revert back to launch a command on the master

[Mattia Rizzolo]

This is an automated email from the git hooks/post-receive script.

mattia pushed a commit to branch master
in repository jenkins.debian.net.

commit 64f663a4b01e0448c7b398cddb8a78a5bf2b166f
Author: Mattia Rizzolo <mattia at debian.org>
Date:   Wed Apr 4 10:58:37 2018 +0200

    doc: the old way to start agent came back at some point, revert back to launch a command on the master
    
    This avoids several doznes of pointless ssh processes and reduces
    latency.
    
    Signed-off-by: Mattia Rizzolo <mattia at debian.org>
---
 INSTALL | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/INSTALL b/INSTALL
index 79045cd..51b0c8f 100644
--- a/INSTALL
+++ b/INSTALL
@@ -102,10 +102,8 @@ Process to follow to add a new node to jenkins:
   * 'Remote root directory': `/srv/jenkins/pseudo-hosts/$hostname`
   * 'Labels': `$arch $short_name` (with '$short_name' like ff64a if the hostname is ff64a-armhf-rb)
   * 'Usage': select "Only build jobs with label expressions matching this node"
-  * 'Launch method': select "Launch slave agents via SSH"
-     * 'Host': `localhost`
-     * 'Credentials': select "jenkins" from the dropdown
-     * 'Prefix Start Slave Command': `/srv/jenkins/bin/start-slave.sh && exit && `
+  * 'Launch method': select "Launch agent via execution of command on the master"
+     * 'Launch command': `/srv/jenkins/bin/start-slave.sh`
   * 'Availability': select "Keep this agent online as much as possible"
 
 The slave setup is done so that the slave.jar program doesn't get run on the remote nodes,

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git