• Fully Compatible
    • STM 2021-05-31
    • 2

      • Branch system_perf.yml for 5.0
        ** Change most references from "master" to "v5.0" Remove the wt-develop variants from the v5.0 commit
        v
        * Branch evergreen.yml for 5.0
        ** After branching, in the 5.0 branch:
        *** Change most references from "master" to "v5.0"
        *** Remove the wt-develop variants from the v5.0 commit See work done in SERVER-35158.

        * Remove wt develop from system-perf.yml and evergreen.yml
        ** Similar to what we've done for previous releases, the wt-develop build variants should be removed from the release MongoDB branches.

        * Update filename suffix to v5.0-latest for nightly builds for 5.0 branch
        ** After branching 5.0, we should follow the same steps we when we branch 4.0 in SERVER-35162.

        * (5.0) Update perf.yml to use 5.0 enterprise module
        ** https://github.com/mongodb/mongo/blob/e291cbea1741b9536340bd67c1311b9fff3381bd/etc/perf.yml#L50 https://github.com/mongodb/mongo/blob/dbb9a7c7acd0c3e97ff128c4eaa225b6567d2249/etc/system_perf.yml#L766
         

        All of these main bullet points should be a separate commit but they should be pushed together in the same commit queue task. The reason they should be pushed as separate commits is in the case of needing to revert one aspect of this entire task.

            Assignee:
            siran.wang@mongodb.com Siran Wang (Inactive)
            Reporter:
            steven.vannelli@mongodb.com Steven Vannelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: