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

Run evergreen evaluate on system_perf.yml as part of the server commit queue

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Performance Analysis
    • Fully Compatible

      We've been hit with a few BFs in the last few months where a commit made the system_perf.yml configuration invalid, which blocks all of our performance tests:

      • BF-32347
      • BF-31108
      • BF-31131

      We could prevent this by adding a task to the server commit queue that runs `evergreen evaluate` on system_perf.yml and checks if it is still valid.

      Bonus points if this task also writes spunk messages, that we can alert on,  if evergreen evaluate returns any warnings. We can not make warnings blocking, since they can be triggered by the project configuration (e.g., patch aliases).

      From Triage:
      Let's see if this is a 1-2 day task but if it's really hard or technically tricky we can deprioritize.

            Assignee:
            john.daniels@mongodb.com John Daniels
            Reporter:
            simon.eismann@mongodb.com Simon Eismann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: