[SERVER-62663] Fix last-continuous binary setup on future git tag buildvariant Created: 14/Jan/22  Updated: 29/Oct/23  Resolved: 25/Jan/22

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

Type: Bug Priority: Major - P3
Reporter: Mikhail Shchatko Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-60210 Create a future git tag evergreen var... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: STM 2022-01-24, STM 2022-02-07
Participants:
Linked BF Score: 43
Story Points: 0

 Description   

Currently we download the latest available binary from mongodb-mongo-master evergreen project as a last-continuous version on future git tag buildvariant. This is not correct for cases, when there is available a binary for a newer commit than the current. We should always download a binary for the commit prior to the current.



 Comments   
Comment by Githook User [ 24/Jan/22 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-62663 Fix last-continuous binary setup on future git tag buildvariant
Branch: master
https://github.com/mongodb/mongo/commit/08f640530638cb1425eaf3836af4b5141de7a50c

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