[CSHARP-4388] Do not run tests locally as part of the release process Created: 27/Oct/22  Updated: 28/Oct/23  Resolved: 28/Oct/22

Status: Closed
Project: C# Driver
Component/s: Build
Affects Version/s: None
Fix Version/s: 2.19.0

Type: Task Priority: Unknown
Reporter: James Kovacs Assignee: James Kovacs
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible

 Description   

When building a release, we currently run the tasks Build, Test, Docs, and Package. The Test task only runs the test suite against a single MongoDB version and topology (likely standalone) on Windows. This local run of the test suite is much less comprehensive than all the variants run on Evergreen. We should only be releasing if Evergreen is suitably green. Sometimes we have flaky tests that cause a local test run to fail even though Evergreen is green. This can slow down the release process as we must re-run the Release task until those flaky tests pass locally.

We have decided to remove the Test task from the Release process (line 54 of build.cake). The release process already highlights the following:

Ensure that the most recent commit is green in Evergreen

This will move us closer to our goal of releasing on Evergreen (CSHARP-3200).



 Comments   
Comment by Githook User [ 28/Oct/22 ]

Author:

{'name': 'James Kovacs', 'email': 'jkovacs@post.harvard.edu', 'username': 'JamesKovacs'}

Message: CSHARP-4388: Removed Test task from Release task. (#917)
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/b4d0204962c3f9bf7fd21e140dddb0f76c840ff2

Generated at Wed Feb 07 21:48:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.