[SERVER-75269] Re-introduce Classic Engine build variant on the 6.3 branch Created: 24/Mar/23  Updated: 29/Oct/23  Resolved: 24/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1, 6.3.2

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: Adi Agrawal
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-81924 Introduce Classic Engine All Feature ... Closed
is related to SERVER-72182 Consider adding Enterprise RHEL 8.0 (... Closed
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.3
Sprint: QE 2023-04-17, QE 2023-05-01
Participants:

 Description   

I noticed that while we are testing the Classic Engine in the 6.0 and master Evergreen waterfalls, we do not appear to have any Classic Engine testing in the 6.3 waterfall. Was this accidental? Since SBE is still very new and large pieces of it were enabled in 6.3, we imagine that some cases could arise in which we advise customers to disable SBE in favor of the Classic Engine. In order to make such a recommendation to a customer with confidence, we need to make sure that the Classic Engine remains fully tested. Therefore, I propose adding dedicated Classic Engine build variant(s) to the 6.3 Evergreen waterfall.



 Comments   
Comment by Githook User [ 27/Apr/23 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'adi.agrawal@mongodb.com', 'username': 'Adityav369'}

Message: SERVER-75269: Add classic engine build variants to evergreen nightly tests

(cherry picked from commit 800862220116f80b6dd68bfa557b16d6a624d97a)
Branch: v7.0
https://github.com/mongodb/mongo/commit/4d48f333e9c8df1e2b66b79f4c6e9dfa5d53722d

Comment by Githook User [ 27/Apr/23 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'adi.agrawal@mongodb.com', 'username': 'Adityav369'}

Message: SERVER-75269: Add classic engine build variants to evergreen nightly tests

(cherry picked from commit 800862220116f80b6dd68bfa557b16d6a624d97a)
Branch: v6.3
https://github.com/mongodb/mongo/commit/df90c9caa05381c1c4e11aa562f5744935b3fbbf

Comment by Githook User [ 24/Apr/23 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'adi.agrawal@mongodb.com', 'username': 'Adityav369'}

Message: SERVER-75269: Add classic engine build variants to evergreen nightly tests
Branch: master
https://github.com/mongodb/mongo/commit/800862220116f80b6dd68bfa557b16d6a624d97a

Comment by Amr Elhelw [ 21/Apr/23 ]

Assigning to adi.agrawal@mongodb.com to start working on this.

Comment by Max Hirschhorn [ 10/Apr/23 ]

kyle.suarez@mongodb.com, the mongodb-mongo-v6.3 Evergreen project uses the evergreen_nightly.yml file as its project configuration whereas the mongodb-mongo-master Evergreen project uses the evergreen.yml file as its project configuration. (Note that there's also a mongodb-mongo-master-nightly Evergreen project which uses the evergreen_nightly.yml file as its project configuration.) Part of the rapid release / stable release branching tasks (e.g. SERVER-72821) include uncommenting lines from the evergreen_nightly.yml file. I think if you're wanting to ensure the Classic Engine build variant continues to be tested as new rapid release and stable release Evergreen projects are created, then moving the Classic Engine build variant into a separate YAML file and having it be included in evergreen_nightly.yml is one option. You may also want to file a STAR ticket as well to ensure the branch processing instructions account for it too.

Comment by Kyle Suarez [ 04/Apr/23 ]

david.storch@mongodb.com mentioned that I should talk to max.hirschhorn@mongodb.com to see if we need to adjust our branching process to prevent us losing coverage like this in the future.

Generated at Thu Feb 08 06:29:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.