[SERVER-26792] Add common source for multiversion setup and tests to get version information Created: 26/Oct/16 Updated: 06/Dec/22 Resolved: 05/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Marko Vojvodic | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | open_todo_in_code, stm, tig-multiversion | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Participants: | |||||||||
| Description |
|
We should have a common place from which both the multiversion setup procedure and multiversion tests (e.g. SERVER-26635) get information about supported major releases. |
| Comments |
| Comment by Brooke Miller [ 05/Nov/21 ] |
|
We believe this was completed recently and there's now a central common yaml config for all of the versions that gets printed as part of the --help message. |
| Comment by Jason Chan [ 29/Jul/20 ] |
|
robert.guo, do you have an idea of the complexity of the work required for this ticket? With continuous delivery, it would be nice to not have to manually update tests like major_version_upgrade.js after each release. Maybe it could be done as part of PM-1803? |