[SERVER-34043] Publish embedded build artifacts to a 'latest' bucket Created: 15/Mar/18 Updated: 29/Oct/23 Resolved: 22/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2018-03-26 |
| Participants: |
| Description |
|
Downstream developers should have a permalink to the latest green build of embedded. |
| Comments |
| Comment by Githook User [ 22/Mar/18 ] | ||||||||||||||
|
Author: {'email': 'acm@mongodb.com', 'name': 'Andrew Morrow', 'username': 'acmorrow'}Message: | ||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 21/Mar/18 ] | ||||||||||||||
|
Will it overwrite if I put the same filename, so that -latest gets updated? | ||||||||||||||
| Comment by Sam Kleinman (Inactive) [ 21/Mar/18 ] | ||||||||||||||
|
The method that the releases use is the s3 copy operation, to very similar effect. | ||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 21/Mar/18 ] | ||||||||||||||
|
Oh neat. I should have thought to look at how the drivers were doing things. I'll see if I can make that work. | ||||||||||||||
| Comment by A. Jesse Jiryu Davis [ 21/Mar/18 ] | ||||||||||||||
|
Can you do this in the Evergreen scripts without Build Team help? In the C Driver's config.yml we have something similar:
If you replaced CURRENT_VERSION with "latest" and made sure the task only runs after success that might do the trick. |