From the course: Running Jenkins on AWS: Deploying and Managing Jenkins on Cloud Infrastructure
Unlock this course with a free trial
Join today to access over 24,900 courses taught by industry experts.
Connect Jenkins to the build server
From the course: Running Jenkins on AWS: Deploying and Managing Jenkins on Cloud Infrastructure
Connect Jenkins to the build server
- [Instructor] Let's connect our Jenkins server to the build server. In this tab, I'm viewing the details for the build server EC2 instance. In another tab, I'm logged into the Jenkins server. We need to get the private DNS for the build server. It's important that we use the private DNS name to keep traffic inside the AWS network. This will reduce costs associated with network traffic and also keep the connection fast. I'll select the link next to the name to copy it to the dashboard. Now, let's go to Jenkins. In Jenkins, I'll select Manage Jenkins and then Nodes. This opens the page where we can manage the Jenkins server and add build servers, which are referred to as nodes. First, let's remove all the executors from the Jenkins server. This will prevent any jobs from starting on the built-in node. On the Configuration page for the built-in node, all we need to do is set the number of executors to zero and select Save. The immediate change we see here is there are no longer any…
Contents
-
-
-
-
Plan the build environment2m 7s
-
(Locked)
Create an IAM role for the build server1m 18s
-
(Locked)
Create a security group and key pair for the build server3m 20s
-
(Locked)
Create the build server1m 34s
-
(Locked)
Connect Jenkins to the build server4m 39s
-
(Locked)
Solution: Set up a build server1m 58s
-
-
-
-
-