Lab
A Cloud Guru

Distributing a Build

In this hands-on lab, we will configure Maven to build a project pulled from SCM — but we will configure a slave node to build the project instead of building the project on the master node.

Try for free Contact sales

Path Info

Level

Advanced

Duration

1h 0m

Published

Nov 16, 2018

Challenge

Configure the Slave Machine for Use with the Jenkins Master
1. Modify the /etc/passwd file on the master to allow the Jenkins user a shell login.
2. Add a password to the jenkins user so you are able to su to that user.
3. Once this is done, su to the jenkins user and run ssh-keygen.
4. Then, as the jenkins user, ssh to the slave machine.
5. Create a jenkins user, add them to sudoers, and create the entry with nopasswd.
6. Exchange the jenkins user's ssh keys with the slave server.
7. Verify key login is working on the slave server.
Challenge

Run the Maven Build on the Remote Agent
1. Create a Maven installation named M3.
2. From Manage Jenkins > Manage Nodes, set up the remote node.
3. Label the node slave1.
4. Create a freestyle project named mavenproject that is set to run only on slave1.
5. Configure it to use M3 maven install.
6. Create a shell build step to run bin/makeindex.
7. Archive the index.jsp and ensure it gets fingerprinted.

Author

A Cloud Guru

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.