[WIP] Add code coverage build definition.

[safern]

This brings us closer to having code coverage with the new build system.

cc: @danmosemsft @ericstj

[safern]

Here is the code coverage build: https://dev.azure.com/dnceng/internal/_build/results?buildId=94565

[safern]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 4 pipeline(s).

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@c776f65). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #35296   +/-   ##
=========================================
  Coverage          ?   93.03%           
=========================================
  Files             ?       35           
  Lines             ?     9833           
  Branches          ?        0           
=========================================
  Hits              ?     9148           
  Misses            ?      685           
  Partials          ?        0

Flag	Coverage Δ
#Debug	93.03% <ø> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c776f65...3dfc99a. Read the comment docs.

[safern]

@ViktorHofer I added: dc42790 to upload coverage.xml to azure and then add the settings to download them to the build machine. This is just dependent on: dotnet/arcade#2103

[safern]

/azp run corefx-outerloop-linux

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[safern]

/azp run corefx-outerloop-windows

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[karelz]

@safern this seems to be blocked stale PR. Can we close it now, or does it serve some active purpose? Thanks!

[safern]

@safern this seems to be blocked stale PR. Can we close it now, or does it serve some active purpose? Thanks!

We're blocked on: https://github.com/dotnet/core-eng/issues/5482 to make progress since we can't make any progress since we're hitting that issue.

[ViktorHofer]

@safern I had to manually merge the changes with master and force pushed.

[ViktorHofer]

Things left for this PR:

• Add ReportGenerator step which bundles all the reports together (in yml)
• Add CodeCovExe step which upload the generated report (in yml). Requires CodeCovExe to be published as a AzDO task. Will work on that.

[safern]

Add ReportGenerator step which bundles all the reports together (in yml)
Add CodeCovExe step which upload the generated report (in yml). Requires CodeCovExe to be published as a AzDO task. Will work on that.

Maybe both steps could be part of the AzDO task? To make it easier for other folks as well.

[ViktorHofer]

ReportGenerator is already a AzDO task. Codecov makes sense to be separated. Usually you won't use both unless you are special

[karelz]

@safern @ViktorHofer is there any update on this? If it is not ready (e.g. due to dependencies in CoreCLR), let's close it, until we can make further progress on it ... thanks!

[safern]

Yeah. We also need to merge with the latest changes in the YAML. We’re mostly blocked on helix issue with long paths.

[ViktorHofer]

Reopening as I'm now going to continue this work and want to have CI support.

[karelz]

@ViktorHofer again looks like stalled for 4 weeks :( ... should we close it again?

[ViktorHofer]

Closing again until I have more time for code coverage.