Allow repository state in multiversion tests to be specified in patch builds

XMLWordPrintableJSON

    • Server Tooling & Methods
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If someone wants to patch-test a change, for example: when testing a 4.2 binary on 4.4, there's no easy way to make sure that the change works effectively on 4.4 and 4.2.

      One way of addressing this might be to use evergreen modules for multiversion testing, so that patch-set-module could be used, if modules of the same repo are supported.

            Assignee:
            Backlog - Server Tooling and Methods (STM) (Inactive)
            Reporter:
            Raiden Worley (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: