From 5b62beccf7dafa33618d0853d24c116d9a4ef097 Mon Sep 17 00:00:00 2001 From: "hamza.suwae" Date: Fri, 7 Aug 2026 14:53:07 +0900 Subject: [PATCH 1/3] ! -- update `PublishCodeCoverageResults@2` references to drop `@1` parameters. `codeCoverageTool` and `reportDirectory` were dropped in `@2`. --- docs/pipelines/customize-pipeline.md | 1 - docs/pipelines/ecosystems/customize-javascript.md | 2 -- docs/pipelines/ecosystems/customize-python.md | 3 +-- docs/pipelines/ecosystems/dotnet-core.md | 1 - docs/pipelines/ecosystems/ruby.md | 4 ---- 5 files changed, 1 insertion(+), 10 deletions(-) diff --git a/docs/pipelines/customize-pipeline.md b/docs/pipelines/customize-pipeline.md index 85ada9da9eb..87d2c6b5311 100644 --- a/docs/pipelines/customize-pipeline.md +++ b/docs/pipelines/customize-pipeline.md @@ -96,7 +96,6 @@ You can add more **scripts** or **tasks** as steps to your pipeline. A task is a - task: PublishCodeCoverageResults@2 inputs: summaryFileLocation: "$(System.DefaultWorkingDirectory)/**/site/jacoco/jacoco.xml" # Path to summary files - reportDirectory: "$(System.DefaultWorkingDirectory)/**/site/jacoco" # Path to report directory failIfCoverageEmpty: true # Fail if code coverage results are missing ``` diff --git a/docs/pipelines/ecosystems/customize-javascript.md b/docs/pipelines/ecosystems/customize-javascript.md index 659f0b6b69f..084ef74bdb3 100644 --- a/docs/pipelines/ecosystems/customize-javascript.md +++ b/docs/pipelines/ecosystems/customize-javascript.md @@ -550,9 +550,7 @@ To publish code coverage results to the server, add the [Publish code coverage r ```yaml - task: PublishCodeCoverageResults@1 inputs: - codeCoverageTool: Cobertura summaryFileLocation: '$(System.DefaultWorkingDirectory)/**/*coverage.xml' - reportDirectory: '$(System.DefaultWorkingDirectory)/**/coverage' ``` #### [Classic](#tab/classic) diff --git a/docs/pipelines/ecosystems/customize-python.md b/docs/pipelines/ecosystems/customize-python.md index dc40922c533..e8943b7745a 100644 --- a/docs/pipelines/ecosystems/customize-python.md +++ b/docs/pipelines/ecosystems/customize-python.md @@ -190,7 +190,6 @@ Add the [Publish code coverage results task](/azure/devops/pipelines/tasks/refer ```yaml - task: PublishCodeCoverageResults@2 inputs: - codeCoverageTool: Cobertura summaryFileLocation: '$(System.DefaultWorkingDirectory)/**/coverage.xml' ``` @@ -220,4 +219,4 @@ You can also use Azure Pipelines to [build an image](containers/build-image.md) - [Getting Started with Python in VS Code](https://code.visualstudio.com/docs/python) - [Build and publish a Python app](python.md) - [Azure Pipelines task reference](/azure/devops/pipelines/tasks/reference) -- [Azure Pipelines agents](../agents/agents.md) \ No newline at end of file +- [Azure Pipelines agents](../agents/agents.md) diff --git a/docs/pipelines/ecosystems/dotnet-core.md b/docs/pipelines/ecosystems/dotnet-core.md index 028ba96fb7b..91bb19274f8 100644 --- a/docs/pipelines/ecosystems/dotnet-core.md +++ b/docs/pipelines/ecosystems/dotnet-core.md @@ -694,7 +694,6 @@ To run tests and publish code coverage with Coverlet: - task: PublishCodeCoverageResults@2 displayName: 'Publish code coverage report' inputs: - codeCoverageTool: 'Cobertura' summaryFileLocation: '$(Agent.TempDirectory)/**/coverage.cobertura.xml' ``` diff --git a/docs/pipelines/ecosystems/ruby.md b/docs/pipelines/ecosystems/ruby.md index 70734a33ac4..9b44faba53d 100644 --- a/docs/pipelines/ecosystems/ruby.md +++ b/docs/pipelines/ecosystems/ruby.md @@ -138,9 +138,7 @@ Add the [Publish Code Coverage Results](/azure/devops/pipelines/tasks/reference/ ```yaml - task: PublishCodeCoverageResults@2 inputs: - codeCoverageTool: Cobertura summaryFileLocation: '$(System.DefaultWorkingDirectory)/**/coverage.xml' - reportDirectory: '$(System.DefaultWorkingDirectory)/**/coverage' failIfCoverageEmpty: true ``` @@ -190,9 +188,7 @@ steps: - task: PublishCodeCoverageResults@2 inputs: - codeCoverageTool: Cobertura summaryFileLocation: '$(System.DefaultWorkingDirectory)/**/coverage.xml' - reportDirectory: '$(System.DefaultWorkingDirectory)/**/coverage' failIfCoverageEmpty: true displayName: 'Publish code coverage' ``` From 124be1e3b050326233566d1e45381e283d4f8516 Mon Sep 17 00:00:00 2001 From: "hamza.suwae" Date: Mon, 10 Aug 2026 11:38:19 +0900 Subject: [PATCH 2/3] ! -- update gulp code coverage sample task PublishCodeCoverageResults@1 -> @2 in customize-javascript --- docs/pipelines/ecosystems/customize-javascript.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pipelines/ecosystems/customize-javascript.md b/docs/pipelines/ecosystems/customize-javascript.md index 084ef74bdb3..164bcb5d58e 100644 --- a/docs/pipelines/ecosystems/customize-javascript.md +++ b/docs/pipelines/ecosystems/customize-javascript.md @@ -548,7 +548,7 @@ To publish JUnit or xUnit test results to the server, add the [Publish test resu To publish code coverage results to the server, add the [Publish code coverage results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v1) task. You can find coverage metrics in the build summary, and you can download HTML reports for further analysis. ```yaml -- task: PublishCodeCoverageResults@1 +- task: PublishCodeCoverageResults@2 inputs: summaryFileLocation: '$(System.DefaultWorkingDirectory)/**/*coverage.xml' ``` From 8116f3d7ddf63bb86889bd6e9e08c5d0428a6136 Mon Sep 17 00:00:00 2001 From: "hamza.suwae" Date: Mon, 10 Aug 2026 11:38:38 +0900 Subject: [PATCH 3/3] ~ -- update publish code coverage results task reference links v1 -> v2 in customize-javascript --- docs/pipelines/ecosystems/customize-javascript.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pipelines/ecosystems/customize-javascript.md b/docs/pipelines/ecosystems/customize-javascript.md index 164bcb5d58e..f2078b35101 100644 --- a/docs/pipelines/ecosystems/customize-javascript.md +++ b/docs/pipelines/ecosystems/customize-javascript.md @@ -253,7 +253,7 @@ To publish test results, use the [Publish test results](/azure/devops/pipelines/ ### Publish code coverage results -If your test scripts run a code coverage tool such as [Istanbul](https://github.com/istanbuljs), add the [Publish code coverage results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v1) task. You can then see coverage metrics in the build summary and download HTML reports for further analysis. +If your test scripts run a code coverage tool such as [Istanbul](https://github.com/istanbuljs), add the [Publish code coverage results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v2) task. You can then see coverage metrics in the build summary and download HTML reports for further analysis. The task expects Cobertura or JaCoCo reporting output. Ensure that your code coverage tool runs with the necessary options to generate the right output, for example `--report cobertura`. @@ -545,7 +545,7 @@ To publish JUnit or xUnit test results to the server, add the [Publish test resu testRunTitle: 'Test results for JavaScript using gulp' ``` -To publish code coverage results to the server, add the [Publish code coverage results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v1) task. You can find coverage metrics in the build summary, and you can download HTML reports for further analysis. +To publish code coverage results to the server, add the [Publish code coverage results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v2) task. You can find coverage metrics in the build summary, and you can download HTML reports for further analysis. ```yaml - task: PublishCodeCoverageResults@2