Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65878

Migration to separate evergreen configurations needs to be completed

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • ALL
    • Dev Platform 2022-05-16, Dev Platform 2022-05-30

      The v6.0 and master branches currently disagree with how nightly runs should be configured. On the master branch, nightly runs are placed in evergreen.yml, but on v6.0 it's in evergreen_nightly.yml. This arrangement causes confusion when backporting and can cause tests we expect to run on both master and v6.0 to become out of sync.

      We should resolve this difference so backports work as expected. Most likely, it will look like naming a file on both master and v6.0 that gets included into evergreen.yml on both branches.

            Assignee:
            ryan.egesdahl@mongodb.com Ryan Egesdahl (Inactive)
            Reporter:
            ryan.egesdahl@mongodb.com Ryan Egesdahl (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: