[GODRIVER-417] Evergreen doesn't start tests automatically Created: 17/May/18 Updated: 22/May/18 Resolved: 22/May/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Igor Kryvenko | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | evergreen | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Hi all. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 22/May/18 ] |
|
Sorry for the frustration and complication here. In addition to working on the Go driver, I also do a bunch of work with Evergreen. Evergreen doesn't have any support exposing patch builds to the public (or any unauthenticated users,) and for a myriad of reasons, this model is unlikely to change. There is an issue on our backlog to track this (EVG-1928) and we definitely want to enable people from outside of the company to be able to take advantage of Evergreen, and are thinking of many ways to enable this. In the next few months, the Evergreen team has a couple of projects that I think will help address some of this issue. First, Evergreen will soon have a "local execution mode" which will make it possible to run some kinds of tests on local systems, which won't require any access to the evergreen service. While this feature is targeting a different use case (e.g. the development of new evergreen configurations and rapid turn around, on hosts that are very similar to the hosts that evergreen tasks run on,) the "local mode" may make it possible to locally reproduce what evergreen would be doing. For the Go driver project, your local environment is likely to be pretty close to Evergreen's. Second, the Evergreen team is working on ways to make running processes and test fixtures (e.g. mongodb clusters/"topologies") in the context of Evergreen tasks. The idea of this feature is to unify and replace a number of parallel tools that we use internally for managing these processes in tests (many of the drivers use a tool called mongo-orchestration to manage these processes, which is difficult to bootstrap.) We hope that this new tool will make the entire process more straight forward, and enable more consistent local reproduction, which will make the need to run evergreen patches less essential. I'm going to close this issue, but do let us know if there's any more context we can provide about specific builds and we'll do our best to proxy information to you. Thanks also again for all of your effort and work. It's very appreciated. Cheers, |