Jenkins Amazon EC2 Plugin: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* https://plugins.jenkins.io/ec2 | * https://plugins.jenkins.io/ec2 | ||
* https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin | |||
* https://blog.iseatz.com/ec2-plugin-jenkins-automatically-provision/ | * https://blog.iseatz.com/ec2-plugin-jenkins-automatically-provision/ | ||
=Internal= | =Internal= | ||
* [[Jenkins Concepts#Plugin|Jenkins Concepts]] | * [[Jenkins Concepts#Plugin|Jenkins Concepts - Plugins]] | ||
* [[Jenkins_Concepts#Amazon_EC2_Cloud|Jenkins Concepts - Amazon EC2 Cloud]] | |||
=Overview= | =Overview= | ||
The Amazon EC2 plugin provisions and manages Amazon EC2 instances used as [[Jenkins_Concepts#Agent|build agents]] as part of a Jenkins [[Jenkins_Concepts#Amazon_EC2_Cloud|"Amazon EC2" agent cloud]]. The EC2 instances are started on demand and terminated as they become unused. The access to agent instances is via SSH, and the plugin requires the configuration of the SSH key pair. The EC2 instances are built off an AMI that is also configured in the plugin. Other instance-specific configuration elements, such as instance type, availability zone, whether to use spot instances or not, the AWS security groups, subnet IDs, IAM instance profile, whether to delete the root device on instance termination, etc. are specified in the plugin's "agent cloud" configuration. | |||
An instance cap can be configured to place an upward limit on the number of EC2 instances that Jenkins may launch. | |||
Latest revision as of 06:00, 20 December 2019
External
- https://plugins.jenkins.io/ec2
- https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin
- https://blog.iseatz.com/ec2-plugin-jenkins-automatically-provision/
Internal
Overview
The Amazon EC2 plugin provisions and manages Amazon EC2 instances used as build agents as part of a Jenkins "Amazon EC2" agent cloud. The EC2 instances are started on demand and terminated as they become unused. The access to agent instances is via SSH, and the plugin requires the configuration of the SSH key pair. The EC2 instances are built off an AMI that is also configured in the plugin. Other instance-specific configuration elements, such as instance type, availability zone, whether to use spot instances or not, the AWS security groups, subnet IDs, IAM instance profile, whether to delete the root device on instance termination, etc. are specified in the plugin's "agent cloud" configuration.
An instance cap can be configured to place an upward limit on the number of EC2 instances that Jenkins may launch.