How to add EC2 plugin to Jenkins server?
From the Services drop down on the top bar, select EC2 Select Instances from the left navigation Menu Find and Select your Jenkins Server Press Actions then from the drop down select Instance Settings – > Add / Replace IAM Role
How to start and stop EC2 slaves in Jenkins?
“This Role is used for jenkins to start and stop ec2 slaves on “servername” Press Create Role; You’ve now created the Policy and Role required for Jenkins to start slaves. Attach your EC2 Role to your Jenkins Master. Logon to the AWS console; From the Services drop down on the top bar, select EC2; Select Instances from the left navigation Menu
What happens if key is not found in Jenkins plugin?
If the key is not found, the plugin doesn’t allow the connection to the instance to guarantee the instance is the right one. If the key is found and it is the same as the one presented by the instance, then it’s saved to be used on future connections, so the console is only checked once. The AMI used should print the key used.
What happens to Jenkins instances when load goes up?
With this setting, your Jenkins will automatically start instances when the load goes up, and the instances will be terminated (or stopped – see below) automatically if it’s idle for more than 30 mins. By default, instances are terminated when the idle timeout period expires.
How to add an IAM role to Jenkins?
On the Add/Replace Role screen, find and select your role, then on the right hand side click Apply. Done! Jenkins now has a IAM role attached to the EC2 instance that can be utilized to Create Slaves.
How does Jenkins pick the right Ami to start?
Windows is currently somewhat supported. Configuring labels allows Jenkins to pick the right AMI to start. For example, if all your existing agents labeled “solaris” are fully busy and you have more builds that are tied to the “solaris” label, Jenkins will start the AMIs that have the “solaris” label.