Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Sebastian Brudziński
Sebastian BrudzińskiReporter
Josh Zamor
Josh Zamor(Deactivated)Labels
Story Points
3
Original estimate
2d 4h
Time tracking
2d 3h logged1h remaining
Sprint
None
Fix versions
Priority
Time Assistant
Time Assistant
Created June 12, 2018 at 5:56 PM
Updated July 13, 2018 at 8:02 AM
Resolved July 13, 2018 at 8:02 AM
Our build queue appears to be getting longer and longer which ties it up and makes developers wait. We should update our worker node AMI to be the latest instance and tools and then provision more worker nodes to drain the build queue faster.
Note: I don't think this will appreciably increase AWS costs as it's the same amount of work to be done, just more will be done in parallel. Unused worker nodes will shut off when they're not needed.
EC2 Plugin page: https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin
AC:
Update the worker node AMI to have the latest OS/tools and the latest instance (M5.large at time of writing).
Provision 2 more worker nodes with 2 executors each.
Turn the node off after 5 min of inactivity
Use the BillTo: OpenLMIS tag
Use the Type: BuildInf tag
Use the name: OpenLMIS-CI-Node OpenLMIS-CI-N (where N is some serial integer)
Don't use the word "slave" anywhere
Open Question
should we instead provision more nodes and limit them to 1 executor? This would be more expensive but we might see fewer random resource contention issues.
Should we use spot instances?