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

Fix/make sure the AWS flavor still works

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • evergreen
    • None
    • Evergreen - Milestone 2

    Description

      Last time I tried, for some reason, it seemed to not be working anymore. We should fix it.

       

      (Ideally, this should also be tested automatically during PR build rather sooner than later. I'm going to make sure we have a Jira filed for this and it's tagged correctly to look into it for M2).

      Attachments

        Issue Links

          Activity

            Confirmed, provisioning the master through the existing CF file works, but EC2 agent provisioning fails. Digging.

            batmat Baptiste Mathus added a comment - Confirmed, provisioning the master through the existing CF file works, but EC2 agent provisioning fails. Digging.

            Fixed https://github.com/jenkins-infra/evergreen/pull/335

            There are still a few issues I found, like JENKINS-54296, but at least we're back to a working state where we can provision a master and agents from the ground up without any configuration.

            batmat Baptiste Mathus added a comment - Fixed https://github.com/jenkins-infra/evergreen/pull/335 There are still a few issues I found, like JENKINS-54296 , but at least we're back to a working state where we can provision a master and agents from the ground up without any configuration.

            People

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

              Dates

                Created:
                Updated:
                Resolved: