[FOLIO-628] Implement Jenkins EC2 plugin to provision temporary Jenkins slave nodes Created: 24/May/17  Updated: 12/Nov/18  Resolved: 26/May/17

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: ci
Remaining Estimate: Not Specified
Time Spent: 7 hours
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-630 Incorporate API-level integration tes... Closed
Sprint:

 Description   

We need to start implementing Jenkin's slave nodes in order to provide additional capacity to partial and full integration testing of the FOLIO stack. Since we use EC2 for CI, it makes sense to use the Jenkins EC2 plugin to manage these nodes since they can be provisioned and terminated dynamically or "as-needed".



 Comments   
Comment by John Malconian [ 26/May/17 ]

Added the Jenkins Slave Ec2 plugin to enable dynamic provisioning of Jenkins Slave nodes. These nodes will be used for some integration tests. The ec2 slave node is a custom Ubuntu Xenial AMI with added configuration for Maven, Gradle, Java 8, Docker, Python, Git, Postgres, etc. It's not a complete FOLIO Build environment. We already have the Docker Slave node for that, but it could so some builds. Maven and Gradle support added with integration testing with those tools in mind.

Generated at Thu Feb 08 23:07:11 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.