[FOLIO-2163] Increase Jenkins build capacity Created: 11/Jul/19  Updated: 03/Jun/20  Resolved: 12/Jul/19

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

Type: Task Priority: P2
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: CP: sprint 67
Story Points: 3
Development Team: Core: Platform

 Description   

Due to proliferation of new repositories, developers, and more unit testing implemented across UI modules, current Jenkins build capacity is strained resulting in some failed jobs specifically where unit tests measure timing. Jobs are also taking longer to complete.



 Comments   
Comment by John Malconian [ 12/Jul/19 ]

Built two additional jenkins build nodes using c5.4xlarge type ec2 instances. The build nodes utilize a lot of CPU more than anything else due to all the webpack builds and unit tests. These instances have 16 cores - double the capacity of the t2.2xlarge systems we've been using. However, after putting them into production, I observed many build failures due to network issues/timeouts. I think there may be an issue with network drivers and Xenial for the C5 instances or probably a step I missed somewhere. As a result, I terminated the C5 instances and added three new t3.2xlarge instances instead. I reduced the amount of parallel builds per node from five to two.

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