[SERVER-54111] Clarify task and task group names in evergreen.yml Created: 28/Jan/21 Updated: 29/Oct/23 Resolved: 29/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Sprint: | Dev Platform 2021-02-08 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The evergreen.yml file has lots of task and task group names that are primarily historical and only loosely associated with what they actually do. Additionally, some tasks like unittests both compile and run the unit tests, making it hard to know whether to attribute slowness to the compile part of the task, or the test execution part of the task. Refactor these names to coherently describe what each task or task group does. Notably, we should not have any task called merely compile, as it is too hard to search for, or understand what it actually does (hint: it currently does no compiling). |
| Comments |
| Comment by Githook User [ 12/Feb/21 ] |
|
Author: {'name': 'Jon Streets', 'email': '65184027+jonstreets@users.noreply.github.com', 'username': 'jonstreets'}Message: STAR-1443 add new tasks from
STAR-1443 improve comments |
| Comment by Githook User [ 29/Jan/21 ] |
|
Author: {'name': 'Andrew Morrow', 'email': 'acm@mongodb.com', 'username': 'acmorrow'}Message: |