[SERVER-59374] backports_required_for_multiversion_testing lacks a means of testing before "deploying" Created: 16/Aug/21  Updated: 15/Sep/21  Resolved: 15/Sep/21

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

Type: Improvement Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Mikhail Shchatko
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-59963 Support multiversion testing on lates... Closed
Sprint: STM 2021-09-20
Participants:
Linked BF Score: 160
Story Points: 0

 Description   

Consider a patch going into the mainline that has a test which can be run under multiversion, but first requires a patch (perhaps the same, perhaps different) to first be backported/pushed to a release branch

The typical workflow for this is:

  • Develop the patch on the latest branch.
  • Add an entry to etc/backports_required_for_multiversion_testing.
  • Do a patch run – when green:
  • Push to mainline
  • Cherry pick or develop a patch on the expected release branch
  • Do a patch run – when green
  • Push to the branch

(Roughly) after that last step a developer does, the mainline branch is eligible to run the test that was previously being skipped over. However, there was no way to test this in a patch run prior to the test being executed as part of a waterfall commit/other people's patch builds. This often creates a lot of testing-only red boxes.

It's not obvious to me we can always safely revert some/all of the patches to get back into a green state.

I couldn't say what a solution looks like, but filing a ticket in hopes of us being able to do something better here.


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