[SERVER-54430] STM Branching Task Created: 09/Feb/21  Updated: 29/Oct/23  Resolved: 22/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Steven Vannelli Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: branch-4.9, during-branch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-50850 STM Branching Task Closed
is related to SERVER-56355 STM Branching Task Closed
is related to SERVER-58831 STM Branching Task Closed
is related to SERVER-61668 STM Branching Task Closed
is related to SERVER-63355 STM Branching Task Closed
is related to SERVER-64833 STM Branching Task Closed
is related to SERVER-68505 STM Branching Task Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-04-05
Participants:
Story Points: 1

 Description   
  • Branch system_perf.yml for 4.9
    ** Change most references from "master" to "v4.9" Remove the wt-develop variants from the v4.9 commit
    v
    * Branch evergreen.yml for 4.9
    ** After branching, in the 4.9 branch:
    *** Change most references from "master" to "v4.9"
    *** Remove the wt-develop variants from the v4.9 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 v4.9-latest for nightly builds for 4.9 branch
    ** After branching 4.9, we should follow the same steps we when we branch 4.0 in SERVER-35162.

    * (4.9) Update perf.yml to use 4.9 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 Githook User [ 22/Mar/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-54430 update perf.yml for 4.9
Branch: v4.9
https://github.com/mongodb/mongo/commit/2c3ca923c73a7f17c8705d8656b07bd4a5c94449

Comment by Githook User [ 22/Mar/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-54430 update system_perf.yml for 4.9
Branch: v4.9
https://github.com/mongodb/mongo/commit/e959acb5cefe92d7cef6d375150aebba84c396a0

Comment by Githook User [ 22/Mar/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-54430 update filename suffix for 4.9
Branch: v4.9
https://github.com/mongodb/mongo/commit/ab59bdc3a177bff3412d950f2b74d3d86a2b4092

Comment by Githook User [ 22/Mar/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-54430 update evergreen.yml for 4.9
Branch: v4.9
https://github.com/mongodb/mongo/commit/61710fe64d2fb1422d8cd48f9156c3407471db9f

Comment by Brooke Miller [ 16/Feb/21 ]

We discussed that we'll rotate this task each quarter among STM engineers. For this release, Rob will take care of it and add the team to the code review for awareness.

Comment by Brooke Miller [ 16/Feb/21 ]

robert.guo  mentioned this is something that we have to do together in the Branching meeting. 

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