{"id":900,"date":"2023-11-07T02:28:00","date_gmt":"2023-11-07T02:28:00","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=900"},"modified":"2023-11-07T02:28:00","modified_gmt":"2023-11-07T02:28:00","slug":"setup-slaves-on-jenkins-2","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=900","title":{"rendered":"How to Setup Jenkins Agent\/Slave Using SSH"},"content":{"rendered":"

In this beginner’s guide, we will walk you through the steps to set up Jenkins agent nodes using SSH (Password and SSH key-based authentication).<\/p>\n

One of the best features of Jenkins is its distributed nature. You can configure multiple build slaves for better segregation and scalability.<\/p>\n

For example, you might want to test a cross-platform code base with a different operating system. In this case, you can set up different Jenkins agents or slaves and run the job against them.<\/p>\n

Also, a Jenkins distributed architecture<\/a> will reduce the load on the master server.<\/p>\n

Setup Jenkins Agents\/Slaves on Jenkins<\/h2>\n

In this guide, I will walk you through the steps for setting up the Jenkins agent node using password and SSH keys.<\/p>\n

There are two ways of authentication for setting up the Linux Jenkins slave agents.<\/p>\n

    \n
  1. Using username and password<\/li>\n
  2. Using ssh keys.<\/li>\n<\/ol>\n

    Also, do check out my Jenkins Docker Based Agent<\/a>. You can scale and manage your Jenkins agent using Docker containers<\/a>.<\/p>\n

    Jenkins Agent Prerequisites<\/h2>\n

    For Jenkins agent configuration, you need to have the following in the slave machines before adding it to the master.<\/p>\n

      \n
    1. Java should be installed on your agent server.<\/li>\n
    2. A valid Linux user account that can perform the required tasks on the agent server. (preferably a sudo user if your job requires elevated privileges)<\/li>\n
    3. Git should be installed as most build job requires git-specific actions.<\/li>\n<\/ol>\n

      Let’s get started with the Jenkins agent node configuration.<\/p>\n

      Create a Jenkins User<\/h2>\n

      It is recommended to execute all Jenkins jobs as a Jenkins user on the Jenkins agent nodes.<\/p>\n

      \n
      Note:<\/strong><\/b> I am using Ubuntu machine as a slave. The steps will be same for other Linux flavours as well<\/div>\n<\/div>\n

      Step 1:<\/strong> Create a Jenkins user and a password using the following command.<\/p>\n

      sudo adduser jenkins --gecos \"\"<\/code><\/pre>\n
      Type a password when prompted. The above commands should create a user and a home directory named Jenkins under “\/home”.<\/p>\n
      Step 2:<\/strong> Now, log in as a Jenkins user.<\/p>\n
      su jenkins<\/code><\/pre>\n
      Step 3: <\/strong>Create a “jenkins-agent<\/code><\/strong>” directory under \/home\/jenkins.<\/p>\n
      mkdir \/home\/jenkins\/jenkins-agent<\/code><\/pre>\n
      Setting up Jenkins Agents\/Slaves using username and password<\/h2>\n
      Step 1: <\/strong>Head over to Jenkins dashboard –> Manage Jenkins –> Nodes<\/p>\n
      \"Jenkins<\/figure>\n
      Step 2: <\/strong>Select the new node option.<\/p>\n
      \"Jenkins<\/figure>\n
      Step 3:<\/strong> Give it a name, select the “permanent agent<\/code>” option and click Create<\/strong>.<\/p>\n
      \"\"<\/figure>\n
      Step 4: <\/strong>Enter the details as shown in the image below and save them.<\/p>\n
      For the credential box, click the add button and enter the agent server username and password. In our case, the username is jenkins<\/code><\/strong> and password is the one you created when you created the Jenkins user on the agent server. This credential will be used by the Jenkins controller to connect to the agent.<\/p>\n
      To know more about each option, click the question mark on the right side of each text box.<\/p>\n
      \"Jnekins<\/figure>\n
      Step 4: <\/strong>Once you click save, the controller will automatically connect to the agent server and configure it as an agent.<\/p>\n
      If the agent is not connected automatically,<\/p>\n
      By following the same steps, you can add multiple servers as Jenkins agent nodes.<\/p>\n
      Setting up Jenkins Agent Using SSH keys<\/h2>\n
      Step 1:<\/strong> Log in to the slave server as a jenkins user.<\/p>\n
      Step 2:<\/strong> Create a .ssh directory and cd into the directory.<\/p>\n
      mkdir ~\/.ssh && cd ~\/.ssh<\/code><\/pre>\n
      Step 3:<\/strong> Create an ssh key pair using the following command. Press enter for all the defaults when prompted.<\/p>\n
      ssh-keygen -t rsa -C \"The access key for Jenkins slaves\"<\/code><\/pre>\n
      Step 4: <\/strong>Add the public to authorized_keys<\/code> file using the following command.<\/p>\n
      cat id_rsa.pub >> ~\/.ssh\/authorized_keys<\/code><\/pre>\n
      Step 5:<\/strong> Now, copy the contents of the private key to the clipboard.<\/p>\n
      cat id_rsa<\/code><\/pre>\n
      Add the SSH Private Key to Jenkins Credentials<\/h3>\n
      Step 1:<\/strong> Go to Jenkins dashboard –> credentials –> Global credentials –> add credentials, select and enter all the credentials as shown below and click ok.<\/p>\n
      \"Jenkins<\/figure>\n
      Connect SSH Jenkins Agent to Master Node<\/h2>\n
      Step 1: <\/strong>Follow the first 3 steps we did for slave configuration using username and password.<\/p>\n
      Step 2: <\/strong>Follow all the configurations in the 4th step as well. But this time, for the launch method, select the credential you created with the SSH key.<\/p>\n
      Test Jenkins Agent\/Slave Nodes<\/h2>\n
      To test the Jenkins agent node or slave, create a sample project and select the option as shown below.<\/p>\n
      \"Jenkins<\/figure>\n
      You need to select the node using the label option. If you start to type the letter the node list will show up.<\/p>\n
      You can then run a simple, shell script operation to check if the Jenkins agent is executing the job.<\/p>\n
      Conclusion<\/h2>\n
      In this tutorial, we learned how to set up slaves for Jenkins. There is no complex step involved in this configuration.<\/p>\n
      When it comes to automating the process, you will need scripts and Jenkins CLI to do this. I will cover that in future posts.<\/p>\n
      Share if you like it and leave a comment if you have queries!!<\/p>\n
      \n
      Ngu\u1ed3n:<\/strong> How to Setup Jenkins Agent\/Slave Using SSH \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
      Source: https:\/\/devopscube.com\/setup-slaves-on-jenkins-2\/<\/p>\n","protected":false},"author":1,"featured_media":901,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-900","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/900","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=900"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/900\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/901"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=900"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=900"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=900"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}