[SERVER-54622] Retrieve back-branch fixture files to assemble multiversion clusters Created: 18/Feb/21  Updated: 29/Oct/23  Resolved: 27/May/21

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

Type: Task Priority: Major - P3
Reporter: Raiden Worley (Inactive) Assignee: Siran Wang (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-multiversion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-54621 Establish a resmoke fixture API Closed
is depended on by SERVER-55296 Support starting enhanced multiversio... Closed
Issue split
split from SERVER-53814 Separate MongoDB config from resmoke Closed
Problem/Incident
Related
related to SERVER-52985 Allow oplogApplicationEnforcesSteadyS... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: STM 2021-04-05, STM 2021-04-19, STM 2021-05-03, STM 2021-05-17, STM 2021-05-31
Participants:
Linked BF Score: 79
Story Points: 5

 Description   

When executing in multiversion mode, resmoke should retrieve the fixture files for the last-lts branch to assemble the multiversion cluster. These files should interact under the common interface defined in SERVER-54621, so fixtures themselves won't need multiversion-specific logic. In the case of sharded clusters or replica sets, the last-lts fixture file will be used for the cluster. (Future tickets will deal with upgrade/downgrade and version-specific edges.)

This ticket should also encompass establishing a method (either a guideline / playbook or automated tool) for changing the API from SERVER-54621 and backporting without temporary redness in the forward branch, to be used here and in the future.

One possibility involves creating a temporary fork of the back-branch containing the backport and pointing the forward-branch at it until the backport is complete.



 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 [ 03/Jun/21 ]

Author:

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

Message: SERVER-54622 Retrieve back-branch fixture files to assemble multiversion

SERVER-57255 Don't delete steady state constraint options when backporting to 5.0

(cherry picked from commit 846a99de9a02454c5649cfaa4e69c785ddbfca62)
Branch: v5.0
https://github.com/mongodb/mongo/commit/93f992a39f79880139bac75cc463dced6b6ea7f8

Comment by Githook User [ 27/May/21 ]

Author:

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

Message: SERVER-54622 Retrieve back-branch fixture files to assemble multiversion

remove task_path_suffix from evergreen_gen_multiversion_tasks.py

replication works

fix fixture API adherence test

generate mongos port on startup

fix sharding and reformat
Branch: master
https://github.com/mongodb/mongo/commit/846a99de9a02454c5649cfaa4e69c785ddbfca62

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