-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Build, WiredTiger
-
Build
-
Storage Non-NYC 2018-03-12, Storage Non-NYC 2018-03-26, Storage Non-NYC 2018-05-07
-
0
-
2
Originally, I had thought that not setting push_path, push_bucket, push_name, and push_arch in the Enterprise Windows 2008R2 WiredTiger develop builder's expansions would be sufficient to make the "push" Evergreen task a no-op; however, I have learned that go-yaml/yaml has known behavior differences in how the merge key "<<:" is implemented (see go-yaml/yaml#81 and go-yaml/yaml#325) that cause it inherit the Enterprise Windows 2008R2 builder's configuration via the enterprise-windows-64-2k8-template anchor. This means that when the "push" task runs on the Enterprise Windows 2008R2 WiredTiger develop builder, the binaries are being uploaded to the same S3 path. The releases for MongoDB happen via the mongo-release Evergreen project, so this issue only impacts the contents of the -latest nightly releases.
- depends on
-
SERVER-34711 Enable burn_in_tests to understand Evergreen task selectors
-
- Closed
-
- duplicates
-
SERVER-35288 Remove push task from development OSX/Windows builds
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
SERVER-31778 Test master with WiredTiger develop
-
- Closed
-