the values config does not work as variables are not evaluated until the step runs, so what actually gets passed and verified against the values config ends up being the string $(variable_name), which always fails as we were saying the value could only be "ado" or "codecov" or ""
This PR updates all yaml files to no longer pass the environment variable as a parameter from MuDevOpsWrapper -> Jobs/PrGate -> Steps/PrGate -> UploadCodeCoverage and instead uses the environment variable directly in UploadCodeCoverage All aforementioned yaml files have been updated with documentation on how to generate code coverage.
the
valuesconfig does not work as variables are not evaluated until the step runs, so what actually gets passed and verified against thevaluesconfig ends up being the string$(variable_name), which always fails as we were saying the value could only be "ado" or "codecov" or ""This PR updates all yaml files to no longer pass the environment variable as a parameter from
MuDevOpsWrapper->Jobs/PrGate->Steps/PrGate->UploadCodeCoverageand instead uses the environment variable directly inUploadCodeCoverageAll aforementioned yaml files have been updated with documentation on how to generate code coverage.