Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Postponed
-
Component/s: evergreen
-
Labels:
-
Similar Issues:
-
Sprint:Evergreen - Milestone 1
Description
We need to at least play and configure a Jenkins to be able to provision agents from an AWS ECS Cluster to get a precise feeling on how hard and what we need to configure it OOTB.
Attachments
Issue Links
- relates to
-
JENKINS-52050 Prototype EC2 agents to get a feeling of what is needed for auto-configuration
-
- Resolved
-
Spent some timeboxed time on Wednesday morning on this as discussed with R. Tyler Croy.
Closing it for now since I feel this requires too much work on AWS and Jenkins sides. Going to favor
JENKINS-52050as a simpler EC2 flavor for now at least, as this seems like the turnaround will be quicker to reach a usable state and be able to start the JEP forJENKINS-51877.