[SERVER-51309] Handle resmoke.ini when changing between branches Created: 02/Oct/20 Updated: 06/Dec/22 Resolved: 10/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: |
| Description |
|
Currently when using the install_dir argument in resmoke.ini and going back to an old branch (experienced on 4.2), you have to change/move resmoke.ini to not include any arguments that didn't exist on those branches. It would be useful to have resmoke ignore arguments (and possibly warn) that are used on newer branches to avoid this. |
| Comments |
| Comment by Robert Guo (Inactive) [ 10/Dec/21 ] |
|
While this is not ideal behavior, we recommend using git worktree for a better cross-branch experience as there may be other cached items that may not be updated correctly. If git worktree is not suitable for any use case, please do reopen this ticket. evergreen host configure creates a worktree for every branch by default |
| Comment by Andrew Morrow (Inactive) [ 05/Mar/21 ] |
|
If you don't want that many worktrees (one for every server release branch), you can also have one worktree for v4.2 and older, and one for v4.4 and newer. The build environment changed dramatically from v4.2 to v4.4. |
| Comment by Robert Guo (Inactive) [ 05/Mar/21 ] |
|
pierlauro.sciarelli You're right that 4.2 does not have the resmoke.ini file. I'd recommend having separate physical working directories for the different branches using git-worktree (or another checkout). Outside of resmoke.ini, Python dependencies change between branches without notice so it's a good idea to have a clean, unique, environment for each branch. |