Use Case

I reached out to the evergreen team to figure out why some of our mainline commits were being unscheduled. The answer seems to be the batchtime: 60 we have set for our evergreen projects. Docs for batchtime:

Batchtime: sets an interval of time in minutes that Evergreen should wait before activating builds/tasks on mainline commits. It will only activate the build/tasks for latest commit. If used with activate true, batchtime will be ignored and the builds/tasks will run every time.

We can use activate to override this for our perf tests. Or just remove the batchtime from our projects.

User Experience

• We want Perf tasks to run on every commit to main, but allow batching for the other build variants

Dependencies

• N/A

Risks/Unknowns

• N/A

Acceptance Criteria

Implementation Requirements

• Ensure perf tests run on every waterfall commit. Ensure this is the case in every repo where we run performance tests (driver and bson).

Testing Requirements

• Test by merging two PRs in quick succession
• Check to make sure perf tasks run for both, and that the full waterfall only runs for latest

Documentation Requirements

• N/A

Follow Up Requirements

• N/A