From 215c1ec3a215d451d37fc709445d40b51d2c3525 Mon Sep 17 00:00:00 2001 From: Benjamin Muschko Date: Fri, 9 Aug 2019 16:07:39 -0600 Subject: [PATCH] Mention passwd for user --- 10-distributed-builds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/10-distributed-builds.md b/10-distributed-builds.md index 3f8da84..c164b46 100644 --- a/10-distributed-builds.md +++ b/10-distributed-builds.md @@ -4,7 +4,7 @@ 1. Go to "Manage Jenkins" > "Manage Nodes". You should see a single `master` node. 2. Configure the `master` node by setting the # of executor value to 0. That will take care of never using the `master` for job workload. -3. Have other physical or virtual machines ready that can act as agent nodes. Log into the machine as `root` user and create a new user named `jenkins` with the command `useradd -d /var/lib/jenkins jenkins`. From the `master` node, copy the contents of the `id_rsa.key` file to the clipboard. Paste the contents of the clipboard to the file `/var/lib/jenkins/.ssh/authorized_keys`. +3. Have other physical or virtual machines ready that can act as agent nodes. Log into the machine as `root` user and create a new user named `jenkins` with the commands `useradd -d /var/lib/jenkins jenkins` and `passwd jenkins`. From the `master` node, copy the contents of the `id_rsa.key` file to the clipboard. Paste the contents of the clipboard to the file `/var/lib/jenkins/.ssh/authorized_keys`. 4. Add new nodes by clicking "New Nodes". Enter an appropriate name and select the option "Permanent Agent". Use the remote directory `/home/jenkins/jenkins_slave` and set the # of executors to 2. Enter the host and provide credentials by selecting "SSH Username with private key". To keep things easy select "Non verifying Verification Strategy". 4. Trigger a build. You should see that the build is only executed on the agent and not the `master` node. 5. Add at least one more agent.