ec2-plugin | Allow Jenkins to start agents | Plugin library

by jenkinsci Java Version: ec2-2.0.7 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | ec2-plugin Summary

ec2-plugin is a Java library typically used in Plugin, Jenkin, Docker applications. ec2-plugin has build file available, it has a Permissive License and it has low support. However ec2-plugin has 49 bugs and it has 1 vulnerabilities. You can download it from GitHub.

Allow Jenkins to start agents on EC2 or Eucalyptus on demand, and kill them as they get unused. With this plugin, if Jenkins notices that your build cluster is overloaded, it'll start instances using the EC2 API and automatically connect them as Jenkins agents. When the load goes down, excess EC2 instances will be terminated. This set up allows you to maintain a small in-house cluster, then spill the spiky build/test loads into EC2 or another EC2 compatible cloud.

Support

Quality

Security

License

Reuse

Support

ec2-plugin has a low active ecosystem.

It has 278 star(s) with 684 fork(s). There are 132 watchers for this library.

It had no major release in the last 12 months.

ec2-plugin has no issues reported. There are 34 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ec2-plugin is ec2-2.0.7

Quality

ec2-plugin has 49 bugs (1 blocker, 0 critical, 16 major, 32 minor) and 696 code smells.

Security

ec2-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ec2-plugin code analysis shows 1 unresolved vulnerabilities (1 blocker, 0 critical, 0 major, 0 minor).

There are 5 security hotspots that need review.

License

ec2-plugin is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

ec2-plugin releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

ec2-plugin saves you 5939 person hours of effort in developing the same functionality from scratch.

It has 12399 lines of code, 925 functions and 172 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed ec2-plugin and discovered the below as its top functions. This is intended to give you an instant insight into ec2-plugin implemented functionality, and help decide if they suit your requirements.

Launches an EC2 agent
Bootstraps a master SSH command
Creates a temporary file for a private key
Connect to the ssh master
Launches the EC2 agent
Finds the key pair associated with this EC2 instance
Gets the instance with the given id
Instantiates the specified agent
Find all nodes that need to be healthy
Compares this object for equality
Terminates the instance
Called when a task is accepted
Gets the AMI image
Start writing stdout to the client
Checks if this object is equal to the specified object
Compares MacData
Props the specified template
Cancels the current instance
Starts the thread to send data to the client
Initialize data structure
Verifies that the host key is valid
Runs the JVM
Resolves the private key
Launches the script and executes the script
Determines the capacity of the given strategy state
Verifies if the host key is valid

Get all kandi verified functions for this library.

ec2-plugin Key Features

No Key Features are available at this moment for ec2-plugin.

ec2-plugin Examples and Code Snippets

No Code Snippets are available at this moment for ec2-plugin.

Community Discussions

Trending Discussions on ec2-plugin

Is it possible to delay jenkins from connecting to a slave before the cloud init script has run

QUESTION

Is it possible to delay jenkins from connecting to a slave before the cloud init script has run

Asked 2018-Nov-05 at 08:41

I have a cloud init script

...

ANSWER

Answered 2018-Nov-05 at 08:41

In the end I decided it was easier to install java and create a new AMI to fully avoid this issue.

I think that perhaps my expectations that cloud init would run fully before connecting might be incorrect, mainly because of this comment in the documentation

Allow enough time for the instance to launch and execute the directives in your user data, and then check to see that your directives have completed the tasks you intended.

Perhaps one approach to help solve this might be to stop sshd in the run commands while things install and then start it again when all done, hopefully Jenkins would then connect only once everything is ready.

Source https://stackoverflow.com/questions/53108868

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ec2-plugin

It's possible to create a separate account for Jenkins using the Amazon IAM feature. Go to the IAM tab in the AWS console and create a user. Then go to the user's Permissions tab and use this policy (change username if your user is not called jenkins):. If you want to launch agents with an IAM Instance Profile, "iam:PassRole" permission is required. If you want to launch Windows agents and use the generated Administrator password, the "ec2:GetPasswordData" permission is also required.
You may upgrade from a Jenkins installation with a former plugin version without this security mechanism. The default strategy for every existing instance is the Check New Soft strategy. This guarantees your jobs are not going to stop working and improves the situation. We recommend, if possible, upgrading to the Check New Hard strategy to be safer against a Man in the Middle attack.
Before securely connecting to the instance, you need to 1) configure the AMI, 2)install the certificate, 3) configure WinRM properly and 4) set the firewall rules to allow the connection. You can find some guidance at the AMI Type field help, under the template configuration on your Jenkins instance.
When the Allow Self Signed Certificate field is checked, the plugin allows self-signed certificates. It means that the plugin neither checks the CA which issued the certificate, nor verifies the host it is connecting to is present on the certificate. If the field is not checked, this kind of certificates are not allowed and both verifications are performed.
The EC2 plugin connects to the instance using either an IP address. It does not use the DNS name. You must configure WinRM with a certificate which includes the IP of the instance. Something like:

Support

For Jenkins, the major configuration change will be if you have a restrictive firewall, since these instances need to connect back to Jenkins. The first configuration change to Jenkins is to change your Jenkins URL option in the Configure Jenkins page to be the external URL to the server. One port that needs to be open is the one that you use to access Jenkins, the other is the JNLP port, which is generally randomly assigned. To set the JNLP port to something predictable, follow the Connection Mechanism section on this page. Jenkins CLI.

Find more information at: