[SERVER-51407] Create evergreen option to test FCV constant changes with a future git tag Created: 07/Oct/20 Updated: 29/Oct/23 Resolved: 01/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Chan | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Repl 2021-07-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In the world of continuous delivery, updating the FCV constants and applying the latest version git tag must be done in sync to avoid multiversion test failures. We should add an evergreen option that will tag the local patch run with a future git tag so that we can have confidence in our patch builds when updating the FCV constants after a release. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] | ||
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! | ||
| Comment by Githook User [ 01/Jul/21 ] | ||
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: | ||
| Comment by A. Jesse Jiryu Davis [ 09/Oct/20 ] | ||
|
I thought this needed a new Evergreen feature, but it could perhaps be implemented just using the existing "parameter" feature, like:
Documentation on parameters here: https://github.com/evergreen-ci/evergreen/wiki/Parameterized-Builds I haven't thought about it in detail, but it seems possible to create an "add_tag" parameter with a default value of "empty". Everywhere in evergreen.yml that a task calls the "git get project" function, follow it with a call to a new "add tag" function. The new function checks if the add_tag parameter is not empty, and does:
|