[SERVER-60873] Rename multiversion-setup to setup-repro-env Created: 21/Oct/21  Updated: 06/Dec/22  Resolved: 10/Dec/21

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

Type: Task Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Duplicate Votes: 0
Labels: dp-qp-stakeholder-request-2021-10
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-60875 Move the multiversion setup portion o... Closed
Duplicate
Assigned Teams:
Server Tooling & Methods
Participants:
Story Points: 2

 Description   

The multiversion setup script should be renamed to better convey its functionality and be more intuitive.

Update the name in:

  • evergreen.yml
  • readme / wiki pages (internal / external) referencing multiversion-setup or setup-multiverison


 Comments   
Comment by Andrew Morrow (Inactive) [ 26/Oct/21 ]

brooke.miller - I think that sounds quite a bit better. Thanks...

Comment by Brooke Miller [ 26/Oct/21 ]

How does setup-repro-env sound, acm?

Comment by Andrew Morrow (Inactive) [ 26/Oct/21 ]

I guess I just don't see that as a "dev" environment. To me, a dev environment is the stuff you need in order to author changes to the product. This still feels like it is about reproducing test failures. Can we bikeshed a different name?

Comment by Robert Guo (Inactive) [ 22/Oct/21 ]

acm the script does the following:
1. downloads evergreen artifacts
2. downloads Evergreen compiled binaries
3. sets up or downloads the Python venv
4. adds a resmoke.py command to run the failing test(s)

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