[SERVER-53103] Remove WT development variants Created: 30/Nov/20  Updated: 29/Oct/23  Resolved: 04/Dec/20

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

Type: Task Priority: Major - P3
Reporter: Kelsey Schubert Assignee: Brad de Vlugt
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Planned Queue
Participants:

 Description   

With the increased frequency of WT drops as well as the work to serialize the commits from a WT drop, there isn't much value in maintaining WT develop variants to test against the tip of the WT branch. We should remove these variants from correctness and performance testing CI.



 Comments   
Comment by Githook User [ 04/Dec/20 ]

Author:

{'name': 'Brad de Vlugt', 'email': 'brad.devlugt@mongodb.com', 'username': 'brad-devlugt'}

Message: SERVER-53103 Remove wtdevelop variants from CI
Branch: master
https://github.com/mongodb/mongo/commit/2cf65466dd5f37bf1daf4658c02534c06d5a9745

Comment by Luke Chen [ 02/Dec/20 ]

kelsey.schubert brad.devlugt  I think those correctness WT develop build variants still play the role of flagging fallouts prior to a WT drop. These days a mongo server patch build preparing for a WT drop still takes a couple of hours to conclude, and the finished WT develop builds (scheduled every 4 hrs) are able to provide a quicker signal.

Could we update the scope of this ticket to only remove performance WT develop build variants, which I believe no one keeps tracking?

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