MongoDB | 2309588

Info

On 6.0 there are the two yml files evergreen.yml and evergreen_nightly.yml, however evergreen.yml on this branch is completely unused. This is confusing for developers and problematic for backports which will backport something from master evergreen.yml into the unused evergreen.yml in 6.0 (automatically).

Top User Comments

JIRAUSER1253549 commented on Fri, 28 Apr 2023 15:44:06 +0000: This could be affecting 7.0 now as well JIRAUSER1253549 commented on Sat, 8 Apr 2023 00:09:35 +0000: I don't feel like we examined the commits closely enough to determine if we lost coverage. I do agree the cursory look we took seemed like not many commits would matter. I would like several hours to examine the commits and see if any changed tasks or variants in a way we might have lost coverage in some backport to 6.0. JIRAUSER1268551 commented on Fri, 7 Apr 2023 23:29:06 +0000: We spoke about this today and it looks like there were no victims for this problem (yet). Should we delete evergreen.yml in v6.0 and replace it with evergreen_nightly.yml? JIRAUSER1253549 commented on Fri, 7 Apr 2023 15:46:19 +0000: Here is the history of commits to the unused evergreen.yml file from 6.0. All of these recent commits could potentially be losing us coverage where the changes were intended to go to evergreen_nightly.yml but did not: https://github.com/mongodb/mongo/commits/v6.0/etc/evergreen.yml

Steps to Reproduce