[CSHARP-1853] Anything that can be run in Evergreen can also be run locally Created: 30/Nov/16 Updated: 02/Oct/20 Resolved: 02/Oct/20 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Stam | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | CSHARP-2438 |
| Description |
|
Evergreen should be treated as a launcher that passes relevant parameters to the build script. The idea is that anything that can be run in Evergreen can also be run locally, either as a faster alternative to a patch build or more importantly when debugging is required. Besides running the entire test suite locally, it should be possible to run individual configurations (matrix entries) locally. |
| Comments |
| Comment by Robert Stam [ 02/Oct/20 ] |
|
The original idea was that you could run the tests locally against any version or configuration of the server. Something like: .\build.ps1 -target test net452 server44 replicaset and the build script would stand up and tear down the cluster automatically to run the tests against (like happens on Evergreen). This no longer seems valuable, for at least two reasons:
Therefore this ticket can be closed as Won't Do. |