The Evergreen tasks that test the driver packages against other projects (test-efcore, test-odata, test-analyzer) and the smoke tests (test-smoke-tests-*) currently depend on push-packages-myget. That task publishes every build to the public MyGet feed so the tasks can restore the freshly built driver package from there. As a result:
- every CI build is published to a public feed, even though only these tasks need the package;
- these tasks cannot run in any Evergreen project that must not publish to MyGet;
- CI depends on MyGet being available.
build-packages already uploads the packages to S3 and download-packages already downloads them. These tasks should restore the driver from the downloaded packages through a local NuGet source instead of MyGet.
Publishing to MyGet stays available as a manual task that anyone can start when something needs to be published there. It no longer runs on every build.
To check as part of this ticket:
- mongo-csharp-analyzer (evergreen/get-driver-version.sh) queries MyGet for the newest MongoDB.Driver prerelease when its DRIVER_VERSION is latest. Once the push is manual, that lane no longer sees new driver builds. Decide whether it matters and who owns it.
- A manually started MyGet push still signs and publishes correctly.
Acceptance criteria:
- test-efcore, test-odata, test-analyzer and the smoke tests pass on Linux and Windows restoring the driver from the local source, with no MyGet push in the build.
- The MyGet push does not run automatically, and a manual run publishes the packages to MyGet.
- Nothing in the Evergreen configuration still restores the driver from MyGet.