[SERVER-24262] tarballs for unit tests, debugsymbols, artifacts, and binaries should have descriptive names. Created: 23/May/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | stm, tig-evgconfig | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Tooling & Methods
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
Currently the purpose/type of each tarball is only indicated by the URI path, not the filename itself. So if you download the files using curl or wget, they are indistinguishable from each other, which is annoying when debugging locally. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Kamran K. [ 15/Aug/16 ] |
|
This is an easy code change in etc/evergreen.yml. The hard part is knowing if push tasks or other downstream tasks rely on the current naming conventions. |
| Comment by Eric Milkie [ 05/Aug/16 ] |
|
This is becoming more important, now that you can spawn a host with the tarballs already downloaded for you. Since they all appear in the same directory, one has no way of discerning which tarball contains what files, other than unpacking all of them randomly. |