[SERVER-65878] Migration to separate evergreen configurations needs to be completed Created: 21/Apr/22  Updated: 05/Jul/23  Resolved: 27/Oct/22

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

Type: Bug Priority: Major - P3
Reporter: Ryan Egesdahl (Inactive) Assignee: Ryan Egesdahl (Inactive)
Resolution: Won't Do Votes: 0
Labels: ULTRA
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-78681 Move BlackDuck to evergreen_nightly.yml Closed
Related
is related to SERVER-68841 Enable Black Duck on 6.0 Closed
Operating System: ALL
Sprint: Dev Platform 2022-05-16, Dev Platform 2022-05-30
Participants:

 Description   

The v6.0 and master branches currently disagree with how nightly runs should be configured. On the master branch, nightly runs are placed in evergreen.yml, but on v6.0 it's in evergreen_nightly.yml. This arrangement causes confusion when backporting and can cause tests we expect to run on both master and v6.0 to become out of sync.

We should resolve this difference so backports work as expected. Most likely, it will look like naming a file on both master and v6.0 that gets included into evergreen.yml on both branches.



 Comments   
Comment by Ryan Egesdahl (Inactive) [ 27/Oct/22 ]

Evergreen is currently working on projects to remove the limits that inspired the addition of nightly.yml in the first place. Also, SDP is working on other projects to reduce the number of build variants and tests that were causing the changeset sizes to be so big. Rather than try to force the issues, we're just going to let this resolve itself naturally via the other efforts.

Comment by Luke Bonanomi [ 21/Apr/22 ]

Apologies, wrong instance!

Generated at Thu Feb 08 06:03:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.