[SERVER-50841] Allow repository state in multiversion tests to be specified in patch builds Created: 09/Sep/20  Updated: 27/Oct/23  Resolved: 05/Nov/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Raiden Worley (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Gone away Votes: 1
Labels: tig-multiversion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

If someone wants to patch-test a change, for example: when testing a 4.2 binary on 4.4, there's no easy way to make sure that the change works effectively on 4.4 and 4.2.

One way of addressing this might be to use evergreen modules for multiversion testing, so that patch-set-module could be used, if modules of the same repo are supported.



 Comments   
Comment by Brooke Miller [ 05/Nov/21 ]

We added support to download arbitrary binaries from patch builds through parameterized builds in PM-1803.

Comment by Brooke Miller [ 15/Sep/20 ]

Instead of doing what was described, we discussed that instead of calling the setup multiversion test in evergreen.yml, engineers could run a curl command that downloads the binary. The mulitversion binaries need to be statically linked.

Generated at Thu Feb 08 05:23:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.