[SERVER-35210] curator release versions should be populated from the project expansions Created: 24/May/18 Updated: 29/Oct/23 Resolved: 01/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.16, 3.6.6, 4.0.0-rc5, 4.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sam Kleinman (Inactive) | Assignee: | Ramon Fernandez Marina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.0, v3.6, v3.4
|
||||
| Participants: | |||||
| Description |
|
we should change the value of curator_release in the server evergreen.yml to use a project expansion, in the form of:
which will let us move forward and try releases across branches and make the process of updating and experiment with evergreen deploys much easier, particularly during release season. |
| Comments |
| Comment by Githook User [ 07/Jun/18 ] |
|
Author: {'name': 'Ramon Fernandez', 'email': 'ramon@mongodb.com'}Message: (cherry picked from commit 2c6bf9ead4270ffce87eda37b032848e89f86bc7) |
| Comment by Githook User [ 07/Jun/18 ] |
|
Author: {'name': 'Ramon Fernandez', 'email': 'ramon@mongodb.com'}Message: (cherry picked from commit 2c6bf9ead4270ffce87eda37b032848e89f86bc7) |
| Comment by Githook User [ 07/Jun/18 ] |
|
Author: {'name': 'Ramon Fernandez', 'email': 'ramon@mongodb.com'}Message: (cherry picked from commit 2c6bf9ead4270ffce87eda37b032848e89f86bc7) |
| Comment by Githook User [ 01/Jun/18 ] |
|
Author: {'name': 'Ramon Fernandez', 'email': 'ramon@mongodb.com'}Message: |