Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Works as Designed
-
None
Description
Some recent investigation and attempts were performed trying to use task tagging feature in Evergreen to avoid duplication of task listing in one Windows variant that's alias-ed to another anchored Windows variant (SERVER-33647). The challenge encountered here is - different tasks inherited from the anchored variant need to be run on different sizes of Windows instances (large vs small), so that we need to apply different "run_on"/"distro" values after using the tag selectors.
Take below code snippet as example, we need tasks covered by ".wtdevelop !.windows-large" tag to use small Windows instance, while tasks covered by ".wtdevelop .windows-large" to use large Windows instance. Please note the "run_on" and "distro" settings here was just a test performed in the patch build, which did not achieve the desired result.
...
|
tasks:
|
- name: compile
|
tags: ["wtdevelop", "windows-large"]
|
...
|
- name: compile_all
|
tags: ["wtdevelop", "windows-large"]
|
...
|
- name: burn_in_tests
|
tags: ["wtdevelop"]
|
...
|
|
- <<: *enterprise-windows-64-2k8-template
|
name: enterprise-windows-64-2k8-wtdevelop
|
...
|
run_on:
|
- windows-64-vs2015-small
|
tasks:
|
- ".wtdevelop !.windows-large"
|
- ".wtdevelop .windows-large"
|
distro:
|
- windows-64-vs2015-large
|
...
|
It would be quite useful to have the tasks field value overriding being supported with the task tagging feature.
Attachments
Issue Links
- is related to
-
SERVER-33647 Enterprise Windows 2008R2 WiredTiger develop shouldn't run the push task
-
- Open
-