[SERVER-56355] STM Branching Task Created: 26/Apr/21  Updated: 29/Oct/23  Resolved: 19/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task Priority: Blocker - P1
Reporter: Steven Vannelli Assignee: Siran Wang (Inactive)
Resolution: Fixed Votes: 0
Labels: branch-5.0, during-branch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-54430 STM Branching Task Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-05-31
Participants:
Story Points: 2

 Description   
  • 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.


 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 18/May/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-56355 update evergreen.yml for 5.0

SERVER-56355 update filename suffix for 5.0

SERVER-56355 update system_perf.yml for 5.0

SERVER-56355 update perf.yml for 5.0
Branch: v5.0
https://github.com/mongodb/mongo/commit/045a0bf9bbae4f04915105bbbf8d8844e2e3dab8

Comment by Githook User [ 18/May/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-56355 update perf.yml for 5.0
Branch: v5.0
https://github.com/mongodb/mongo/commit/9282e11fde3841fd2fbe38f53b140e771a57968b

Comment by Githook User [ 18/May/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-56355 update system_perf.yml for 5.0
Branch: v5.0
https://github.com/mongodb/mongo/commit/9894c953644913b2985c7d6e07c4deb8355bba71

Comment by Githook User [ 18/May/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-56355 update filename suffix for 5.0
Branch: v5.0
https://github.com/mongodb/mongo/commit/cf978b065c92ad48c1bc9f1c781eb9f789472bfe

Comment by Githook User [ 18/May/21 ]

Author:

{'name': 'Siran Wang', 'email': 'siran.wang@mongodb.com', 'username': 'vincivans'}

Message: SERVER-56355 update evergreen.yml for 5.0
Branch: v5.0
https://github.com/mongodb/mongo/commit/6d0c809bd19dafe14a4cca89d497badaabb023c5

Generated at Thu Feb 08 05:39:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.