Conversation
There was a problem hiding this comment.
Pull request overview
Updates Evergreen’s MongoDB bootstrap step to use the newer run-mongodb.sh entrypoint (with start) instead of run-orchestration.sh, aligning CI provisioning with the mongodb-runner flow referenced by the PR title.
Changes:
- Switch
bootstrap-mongo-orchestrationto call${DRIVERS_TOOLS}/.evergreen/run-mongodb.sh start. - Apply the same change in the generated Evergreen config to keep it in sync with the template.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .evergreen/config/common.yml.erb | Updates the bootstrap function to start MongoDB via run-mongodb.sh start. |
| .evergreen/config.yml | Regenerates the generated Evergreen config with the same updated bootstrap command. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| include_expansions_in_env: [TOPOLOGY, AUTH, SSL, ORCHESTRATION_FILE, | ||
| REQUIRE_API_VERSION, LOAD_BALANCER] | ||
| args: ["${DRIVERS_TOOLS}/.evergreen/run-orchestration.sh"] | ||
| args: ["${DRIVERS_TOOLS}/.evergreen/run-mongodb.sh", "start"] |
There was a problem hiding this comment.
bootstrap-mongo-orchestration now invokes run-mongodb.sh start, but the function name (and downstream references like “run tests with orchestration…”) still describe the old mongo-orchestration flow. This mismatch makes the Evergreen config harder to understand/maintain; consider renaming the function (and any related labels) to reflect the mongodb-runner/mongodb bootstrap it performs.
| include_expansions_in_env: [TOPOLOGY, AUTH, SSL, ORCHESTRATION_FILE, | ||
| REQUIRE_API_VERSION, LOAD_BALANCER] | ||
| args: ["${DRIVERS_TOOLS}/.evergreen/run-orchestration.sh"] | ||
| args: ["${DRIVERS_TOOLS}/.evergreen/run-mongodb.sh", "start"] |
There was a problem hiding this comment.
This generated config still calls the function bootstrap-mongo-orchestration, but it now runs run-mongodb.sh start. To avoid confusion when debugging CI failures, consider renaming the function (and any associated task/function labels that mention orchestration) to reflect the new bootstrap mechanism.
No description provided.