Add mongot as a module for server evergreen project

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Development Platform
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
            Reporter:
            Ted Tuckman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: