Following SERVER-82708 a prioritised subset of build variants are being run on existing release branches. This ticket will involve setting up perf.yml to make the branching process (and only including this prioritised subset of variants) easier for the release team. One possible solution is to use file includes and have a setup similar to evergreen_nightly.yml.
For more context on the existing releasing branching process see this document.
The following are the list of variants that should be included when branching (the workloads for each variant should match master but do not need to be run at any special cron (just the default)):
perf-atlas-M60-real.arm.aws.2023-11 |
perf-atlas-M60-real.intel.azure.2023-11 |
perf-3-shard.arm.aws.2023-11 |
perf-3-node-replSet.arm.aws.2023-11 |
perf-3-node-replSet-intel.intel.aws.2023-11 |
perf-2-node-replSet-initialsync.arm.aws.2023-11 |
perf-mongo-perf-standalone.arm.aws.2023-11 |
perf-mongo-perf-standalone.intel.aws.2023-11 |
perf-standalone.arm.aws.2023-11 |
perf-shard-lite-fle.arm.aws.2023-11 |
- related to
-
SERVER-86477 Add back default-sharding (single-shard-colocated-mongos) variants to sys perf
- Closed