[SERVER-41940] Remove use of evergreen_client library in favor of evergreen.py in burn_in_tests Created: 26/Jun/19 Updated: 29/Oct/23 Resolved: 08/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Lydia Stepanek (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | techdebt, tig-burnin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | DAG 2019-07-15 |
| Participants: | |
| Story Points: | 2 |
| Description |
|
The burn_in_tests script calls out to evergreen to get test history and other information about the task running. We recently build a python evergreen client and added it to the burn_in_tests buildscript. We should be consistent and use evergreen.py to access the evergreen api everywhere in the burn_in_tests script. As a mongo engineer AC
Related ticket: https://jira.mongodb.org/browse/SERVER-40893 |
| Comments |
| Comment by Githook User [ 08/Jul/19 ] |
|
Author: {'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}Message: |