[SERVER-74696] Add mongot as a module for server evergreen project Created: 08/Mar/23  Updated: 09/Mar/23  Resolved: 08/Mar/23

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

Type: New Feature Priority: Major - P3
Reporter: Ted Tuckman Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Assigned Teams:
Server Development Platform
Participants:

 Description   

It would be useful to have a variant or evergreen task that allows putting up patches with changes to both 10gen/mongo and 10gen/mongot. It seems like this is doable (with a bit of investigation around builds, more below), by adding mongot as a module and adding the ability to specify the address of the mongot to mongod at startup for the given task.

As a starting point it would be enough to add this as a non-required variant that uses the same hardware with linux as any other variant with all feature flags, and only have it run for patch builds (not on waterfall). While this would be a good starting point, eventually we'd likely want to run it automatically with some cadence.

It seems like adding mongot as a module is straightforward, but unlike enterprise mongot has its own evergreen config. After adding the module and cloning the repo, we'd have to build both mongo and mongot. The current mongot evergreen build command is here, but I'm not sure how that would integrate with the mongo server evergreen config or whether it would need its own copy of the instructions.

Eventually it would also be useful to do this for performance, but having this for correctness tests would be a huge win in itself, and allow us to catch bugs much earlier in the development process.


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