[SERVER-42144] Remove use of evergreen /rest/v1 API in favor of evergreen.py in bypass_compile_and_fetch_binaries.py Created: 10/Jul/19 Updated: 29/Oct/23 Resolved: 01/Aug/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 | Assignee: | Lydia Stepanek (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | DAG 2019-08-12 |
| Participants: | |
| Story Points: | 3 |
| Description |
|
The bypass_compile_and_fetch_binaries and burn_in_tags_bypass_compile_and_fetch_binaries scripts call out to the evergreen API to get build ids for a given revision. We recently built 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. Currently, the scripts call this endpoint directly: Instead, they can use evergreen.py to call this v2 endpoint: ------------------------------------------------------ As a mongo engineer AC
------------------------------------------------------ Related tickets: |
| Comments |
| Comment by Githook User [ 01/Aug/19 ] |
|
Author: {'name': 'Lydia Stepanek', 'username': 'lydiastepanek', 'email': 'lydia.stepanek@mongodb.com'}Message: |
| Comment by Lydia Stepanek (Inactive) [ 01/Aug/19 ] |