[SERVER-69574] Upload list of all collections from js/core tests to artifact tarball Created: 09/Sep/22 Updated: 10/Feb/23 Resolved: 22/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Rohan Sharan | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | milestone-4, rep-160-milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
In mongosync, it is becoming important for us to have a comprehensive list of collections that exist at the end of the
We'd like this list to be written to a file and uploaded to the artifact tarball for each mongo server evergreen run for a specific commit, so that this file can be later accessed from the artifact tarball by mongosync using db-contrib-tool. It doesn't matter to me which task in the mongo server repo actually does the uploading. This ticket is also not necessarily a request to implement this fully, it is acceptable for an engineer on mongosync to do the implementation of this, as long as it makes sense to someone on the SERVER team and they can support the mongosync engineer. |
| Comments |
| Comment by Rohan Sharan [ 22/Sep/22 ] |
|
We decided to go with a different approach, so I will close this ticket for now. |
| Comment by Rohan Sharan [ 19/Sep/22 ] |
|
Yes good point. This shouldn't be scheduled until it is clear that this is the solution we will proceed with (there is another potential solution). I will comment here when we have decided. |