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

STM Branching Task

XMLWordPrintableJSON

    • Fully Compatible
    • DAG 2022-09-05
    • 1

      • Branch system_perf.yml for 6.1
        • Change most references from "master" to "v6.1" Remove the wt-develop variants from the v6.1 commit
      • Branch evergreen.yml for 6.1
        • After branching, in the 6.1 branch:
          • Change most references from "master" to "v6.1"
      • Remove the wtdevelop variants from the v6.1 commit See work done in SERVER-35158.
      • Remove wtdevelop from system-perf.yml and evergreen.yml
        • Similar to what we've done for previous releases, the wtdevelop build variants should be removed from the release MongoDB branches.
      • The required variants (those starting with "!", except all feature flags) need to be copied to the release project, in addition to changing the include files at the top of the new evergreen.yml file as indicated by the comments here: https://github.com/mongodb/mongo/blob/9dc379a3461ca74dc448330d5f156bfe45d7eaeb/etc/evergreen_nightly.yml#L7-L12
      • Copy Commit Queue buildvariant to evergreen_nightly.yml
      • Update filename suffixes in generate_version_expansions.py to v6.1-latest for nightly builds for 6.1 branch
        • After branching 6.1, we should follow the same steps we when we branch 4.0 in SERVER-35162.
      • (6.1) Update perf.yml to use 6.1 enterprise module
      • Disable renew_ssl_cert in sys-perf on old branches
      • Remove all feature flags buildvariants from system-perf.yml

        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:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Reporter:
            britt.snyman@mongodb.com Britt Snyman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: