[SERVER-72023] Accommodate rapid_release_only tasks Created: 09/Dec/22 Updated: 16/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tausif Rahman (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Correctness
|
| Participants: |
| Description |
|
https://mongodb.slack.com/archives/GPZ8BPS3E/p1670615702122179 Atlas always uses the latest rapid release version on a branch. So, when a new rapid release version comes out, Atlas specific features no longer need to be tested on the old version. An example of this is serverless tests. Essentially we only want to run Atlas specific tasks (serverless) in evergreen for rapid releases and need a way to specify tasks that only run for rapid releases. We could manually stop running tasks on certain branches, but that is manual. Instead we can leverage mongo-task-generator. We could start passing in a new var (ie: rapid_release_only) to the "generate resmoke tasks" function & then add the appropriate logic |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 13/Dec/22 ] |
|
Note that the fact that lts releases are part of the rapid release series is part of what makes this difficult. (Serverless runs on 5.2, 5.3, 6.0, 6.1, 6.2, etc.). We do want to run the serverless tests on 6.0 while Serverless is on 6.0, until Serverless is upgraded 6.1 (and won't downgrade back). But we don't want to continue running serverless tests on 6.0 beyond that, even though the 6.0 branch will remain open and continue receiving commits until it is EOL'd through the lts branch EOL process. |