Test CI (please ignore)

[dilijev]

See #4767

[dilijev]

@dotnet-bot test dailies please

[dilijev]

@dotnet-bot test this please

[dilijev]

@Penguinwizzard want to take a look at the static analysis failures?

[dilijev]

Note: tasks with dailies trigger are not generated for *-ci branches, so we'll have to check those after merging the change. Luckily failures in dailies are non-blocking. I don't see an obvious way to generate those tasks so they don't actually run the dailies for this branch on a daily trigger without writing a different generator which is special-purposed to the *-ci branches.

FYI @MSLaguana @boingoing

[dilijev]

Good things:

Forced Dev14 detection for Legacy config is working:

https://ci2.dot.net/job/Microsoft_ChakraCore/job/release_1.8-ci/job/ci_legacy_x64_debug_prtest/1/console

16:20:49 D:\j\w\ci_legacy_x64---9dce0ce9>call .\jenkins\buildone.cmd x64 debug msbuild14 
16:20:49 Skipping Dev15 and trying Dev14...
16:20:50 MSBuild located at "C:\Program Files (x86)\msbuild\14.0\Bin"

Detection of Dev15 in modern config succeeded:

16:23:34 D:\j\w\arm_release_p---fdf127d1>call .\jenkins\buildone.cmd arm release  "/p:runcodeanalysis=true" 
16:23:34 Trying to locate Dev15...
16:23:34 MSBuild located at "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin"

Dev15 prefast ran under Windows *_release and detected issues based on new heuristics.

That's everything I was hoping for :)