Repo File Sync: MuDevOpsWrapper.yml - Add code coverage calculation parameter #612
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uefibot
force-pushed
the
repo-sync/mu_devops/default
branch
2 times, most recently
from
6a387a6
to
ec7a7bf
Compare
makubacki
changed the title
makubacki
changed the title
makubacki
approved these changes
Nov 6, 2023
|
/AzurePipelines help |
Supported commands
See additional documentation. |
|
/AzurePipelines list |
|
CI/CD Pipelines for this repository: |
|
/AzurePipelines run |
|
Azure Pipelines failed to run 2 pipeline(s). |
|
Waiting for the sync to be amended after microsoft/mu_devops#268 is completed. |
|
/AzurePipelines run |
|
Azure Pipelines failed to run 2 pipeline(s). |
Signed-off-by: Project Mu UEFI Bot <uefibot@microsoft.com>
uefibot
changed the title
uefibot
force-pushed
the
repo-sync/mu_devops/default
branch
from
ec7a7bf
to
dbdecdd
Compare
makubacki
changed the title
Javagedes
approved these changes
Nov 6, 2023
ProjectMuBot
added a commit
to microsoft/mu_tiano_platforms
that referenced
this pull request
Nov 7, 2023
Introduces 4 new commits in [MU_BASECORE](https://github.com/microsoft/mu_basecore.git). <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/mu_basecore/commit/37f7e6f36bce459a8a3e9f28891da7fd528f0427">37f7e6</a> pip: update edk2-pytool-library requirement from ~=0.19.1 to ~=0.19.3 (<a href="https://github.com/microsoft/mu_basecore/pull/606">#606</a>)</li> <li><a href="https://github.com/microsoft/mu_basecore/commit/bf28b4538ebbe1278ae39db95ced07969e3ff6bc">bf28b4</a> MdePkg/GoogleTest: Add GetTime() RT service mock interface (<a href="https://github.com/microsoft/mu_basecore/pull/607">#607</a>)</li> <li><a href="https://github.com/microsoft/mu_basecore/commit/01abd5c3da33292970d8357459525b9b7454ba42">01abd5</a> BaseTools/Plugin/RustEnvironmentCheck: Add rust-src component check (<a href="https://github.com/microsoft/mu_basecore/pull/611">#611</a>)</li> <li><a href="https://github.com/microsoft/mu_basecore/commit/ae4776d1888fe4c9d5cd71e1fb62b9a295e08e06">ae4776</a> Repo File Sync: MuDevOpsWrapper.yml - Add code coverage calculation parameter (<a href="https://github.com/microsoft/mu_basecore/pull/612">#612</a>)</li> </ul> </details> Signed-off-by: Project Mu Bot <mubot@microsoft.com>
5 tasks
Javagedes
added a commit
that referenced
this pull request
Nov 7, 2023
## Description #612 added an additional `MuDevOpsWrapper.yml` parameter configuration to opt in or out of code coverage, with the default being `false`, disabling code coverage. This was due to the fact that uploading code coverage data required a minimum `edk2-pytool-extensions` and `edk2-pytool-library` version and associated `ParseSettingsManager` to be implemented. This commit upgrades Edk2-pytools to the required version, implements `ParseSettingsManager`, and re-enables code coverage. This change only restores previous functionality, with the caveat that code coverage data is now organized by INF rather than by test executable. This change results in no impact to consumers of MU_BASECORE, however maintainers and contributors may view code coverage results by selecting the pipeline in github and navigating to the pipeline run located at `dev.azure.com`  - [ ] Impacts functionality? - **Functionality** - Does the change ultimately impact how firmware functions? - Examples: Add a new library, publish a new PPI, update an algorithm, ... - [ ] Impacts security? - **Security** - Does the change have a direct security impact on an application, flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter validation improvement, ... - [ ] Breaking change? - **Breaking change** - Will anyone consuming this change experience a break in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call a function in a new library class in a pre-existing module, ... - [ ] Includes tests? - **Tests** - Does the change include any explicit test code? - Examples: Unit tests, integration tests, robot tests, ... - [ ] Includes documentation? - **Documentation** - Does the change contain explicit documentation additions outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation on an a separate Web page, ... ## How This Was Tested N/A ## Integration Instructions No impact to consumers of MU_BASECORE, however maintainers and contributors may view code coverage results by selecting the pipeline in github and navigating to the pipeline run located at `dev.azure.com`
kenlautner
pushed a commit
that referenced
this pull request
Dec 14, 2023
…arameter (#612) synced local file(s) with [microsoft/mu_devops](https://github.com/microsoft/mu_devops). 🤖: View the [Repo File Sync Configuration File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml) to see how files are synced. --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#6774774926](https://github.com/microsoft/mu_devops/actions/runs/6774774926) Signed-off-by: Project Mu UEFI Bot <uefibot@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Dec 14, 2023
## Description #612 added an additional `MuDevOpsWrapper.yml` parameter configuration to opt in or out of code coverage, with the default being `false`, disabling code coverage. This was due to the fact that uploading code coverage data required a minimum `edk2-pytool-extensions` and `edk2-pytool-library` version and associated `ParseSettingsManager` to be implemented. This commit upgrades Edk2-pytools to the required version, implements `ParseSettingsManager`, and re-enables code coverage. This change only restores previous functionality, with the caveat that code coverage data is now organized by INF rather than by test executable. This change results in no impact to consumers of MU_BASECORE, however maintainers and contributors may view code coverage results by selecting the pipeline in github and navigating to the pipeline run located at `dev.azure.com`  - [ ] Impacts functionality? - **Functionality** - Does the change ultimately impact how firmware functions? - Examples: Add a new library, publish a new PPI, update an algorithm, ... - [ ] Impacts security? - **Security** - Does the change have a direct security impact on an application, flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter validation improvement, ... - [ ] Breaking change? - **Breaking change** - Will anyone consuming this change experience a break in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call a function in a new library class in a pre-existing module, ... - [ ] Includes tests? - **Tests** - Does the change include any explicit test code? - Examples: Unit tests, integration tests, robot tests, ... - [ ] Includes documentation? - **Documentation** - Does the change contain explicit documentation additions outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation on an a separate Web page, ... ## How This Was Tested N/A ## Integration Instructions No impact to consumers of MU_BASECORE, however maintainers and contributors may view code coverage results by selecting the pipeline in github and navigating to the pipeline run located at `dev.azure.com`
kenlautner
pushed a commit
that referenced
this pull request
Dec 14, 2023
…arameter (#612) synced local file(s) with [microsoft/mu_devops](https://github.com/microsoft/mu_devops). 🤖: View the [Repo File Sync Configuration File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml) to see how files are synced. --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#6774774926](https://github.com/microsoft/mu_devops/actions/runs/6774774926) Signed-off-by: Project Mu UEFI Bot <uefibot@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Dec 14, 2023
## Description #612 added an additional `MuDevOpsWrapper.yml` parameter configuration to opt in or out of code coverage, with the default being `false`, disabling code coverage. This was due to the fact that uploading code coverage data required a minimum `edk2-pytool-extensions` and `edk2-pytool-library` version and associated `ParseSettingsManager` to be implemented. This commit upgrades Edk2-pytools to the required version, implements `ParseSettingsManager`, and re-enables code coverage. This change only restores previous functionality, with the caveat that code coverage data is now organized by INF rather than by test executable. This change results in no impact to consumers of MU_BASECORE, however maintainers and contributors may view code coverage results by selecting the pipeline in github and navigating to the pipeline run located at `dev.azure.com`  - [ ] Impacts functionality? - **Functionality** - Does the change ultimately impact how firmware functions? - Examples: Add a new library, publish a new PPI, update an algorithm, ... - [ ] Impacts security? - **Security** - Does the change have a direct security impact on an application, flow, or firmware? - Examples: Crypto algorithm change, buffer overflow fix, parameter validation improvement, ... - [ ] Breaking change? - **Breaking change** - Will anyone consuming this change experience a break in build or boot behavior? - Examples: Add a new library class, move a module to a different repo, call a function in a new library class in a pre-existing module, ... - [ ] Includes tests? - **Tests** - Does the change include any explicit test code? - Examples: Unit tests, integration tests, robot tests, ... - [ ] Includes documentation? - **Documentation** - Does the change contain explicit documentation additions outside direct code modifications (and comments)? - Examples: Update readme file, add feature readme file, link to documentation on an a separate Web page, ... ## How This Was Tested N/A ## Integration Instructions No impact to consumers of MU_BASECORE, however maintainers and contributors may view code coverage results by selecting the pipeline in github and navigating to the pipeline run located at `dev.azure.com`
kenlautner
pushed a commit
that referenced
this pull request
Dec 16, 2023
…arameter (#612) synced local file(s) with [microsoft/mu_devops](https://github.com/microsoft/mu_devops). 🤖: View the [Repo File Sync Configuration File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml) to see how files are synced. --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#6774774926](https://github.com/microsoft/mu_devops/actions/runs/6774774926) Signed-off-by: Project Mu UEFI Bot <uefibot@microsoft.com>
kenlautner
pushed a commit
that referenced
this pull request
Dec 18, 2023
…arameter (#612) synced local file(s) with [microsoft/mu_devops](https://github.com/microsoft/mu_devops). 🤖: View the [Repo File Sync Configuration File](https://github.com/microsoft/mu_devops/blob/main/.sync/Files.yml) to see how files are synced. --- This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#6774774926](https://github.com/microsoft/mu_devops/actions/runs/6774774926) Signed-off-by: Project Mu UEFI Bot <uefibot@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
synced local file(s) with microsoft/mu_devops.
🤖: View the Repo File Sync Configuration File to see how files are synced.
This PR was created automatically by the repo-file-sync-action workflow run #6774774926