▬▬▬▬▬▬ Chapters With Timestamps ⏰ ▬▬▬▬▬▬ 0:00 Intro 0:54 Why We need Jenkins to Scale? 2:06 Create and configure AWS EC2 instance to add as a slave 4:31 Install Java into Slave node 5:19 Add linux-slave user for Jenkins slave node & verify the newly created user 6:04 Set new password for the new user, then add the user to sudo group and verify the same 6:20 Login as the new user and setup ssh certificates and complete necessary steps 8:43 Configuring Master node to add and connect with slave node 16:48 Create a Jenkins build project and run inside slave node 19:15 Scale Jenkins on AWS Cloud: Install and Configure Jenkins AWS EC2 Plugin 20:51 Add EC2 role access to the master instance so that it can create necessary resources (Slave node) as required 23:46 Create and configure EC2 Keypair so that Jenkins Master can connect with newly created slave nodes via the private key 25:41 Getting AMI ID EASY WAY 28:17 Adding Lebel 28:30 Create and configure EC2 Security Group 30:53 Running build project in specific AWS Ec2 Cloud Node 32:59 Troubleshooting & Fix the SSH Access 34:08 Running Build Projects Successfully
Hi, Thanks for the video. I followed the steps you mentioned. But i always get a 404 error after the java installation and verification on the logs. Hence the slave node connection fails. What could be the reason?
Hi Sandip, your video is awesome and it helps a lot... really appreciate your efforts here... I have one question in the AWS part where you automate the ec2 instances. how did you install java on the new node through automation as Java is the prerequisite for the slave nodes (if I am correct)... or does it not required to install anyway.. please respond... Thanks
A beautiful video. Thank You for creating this. Is it possible to have master node onprem and slave in AWS with VPN? Will it autoscale or need to create slave node manually? Please help.
In most cases it's the permission issue, but feel free to let me in detail the steps you have followed (just to confirm), mail me here: contact@sandipdas.in, also attach the Jenkins agent logs
You can use available plugins for the same , and add retrying mechanism , but anyway I think default retrying mechanism is there and after fixing the issue manually too you can run the build again, so you have all the options.
@@learnTechWithSandip Hi sandip, Are you provide completed devops tutorial or any classs. Bcz once I m. Getting to subscribe your channel. It's ask to pay So i want to know that what is subscribe plan ؟؟؟
By default the plugin handle that part , but in advance option of the Ec2 plugin you can change that option, like after how many hour the machine should stop
