Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50281

Support splitting tasks differently in mainline vs patch builds

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Testing Infrastructure
    • Labels:
      None

      Description

      Since getting results from mainline builds is usually doesn't have someone waiting for it like patch builds do, we may want to make different tradeoffs when splitting tasks in the maintain vs splitting tasks in patch builds. We are already treating dependencies differently for splitting tasks in patch builds vs mainline builds. So also applying that to the number of tasks split should be fairly straight-forward.


      As an evergreen server maintainer,
      I want to be able to specify different task splitting configurations for mainline vs patch builds,
      So that I can customize how tasks are split based on the situation.


      AC:

      • mainline builds and patch builds can have different targets for number of tasks to split.
      • mainline builds cap the numbers of subtasks to 1.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-dag Backlog - Decision Automation Group (DAG)
            Reporter:
            david.bradford David Bradford
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: