Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52049

Prototype ECS agents to get a feeling of what is needed for auto-configuration

    XMLWordPrintable

    Details

    • 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

            Activity

            Hide
            batmat Baptiste Mathus added a comment -

            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-52050 as 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 for JENKINS-51877.

            Show
            batmat Baptiste Mathus added a comment - 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-52050 as 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 for JENKINS-51877 .

              People

              Assignee:
              batmat Baptiste Mathus
              Reporter:
              batmat Baptiste Mathus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: