Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: PublishCodeCoverageResultsV1 Where it the publish directory? #19897

Closed
1 of 4 tasks
ranouf opened this issue May 21, 2024 · 1 comment
Closed
1 of 4 tasks

Comments

@ranouf
Copy link

ranouf commented May 21, 2024

Task name

PublishCodeCoverageResults

Task version

1

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows

Question

Hi,

I use PublishCodeCoverageResultsV1 in Azure Dev Ops Classic editor. I would like to mv the artefact from Code Coverage Report_$(Build.BuildNumber)" to "Reports"

Here is the command line:
mv "$(Build.ArtifactStagingDirectory)/Code Coverage Report_$(Build.BuildNumber)" "$(Build.ArtifactStagingDirectory)/Reports"

But I have this error:
mv: cannot stat 'D:\a\1\a/Code Coverage Report_10499': No such file or directory

From my understanding, the shortcut $(Build.ArtifactStagingDirectory) is where the artifact is supposed to be published.

Where can I find the artefact generated by PublishCodeCoverageResultsV1?

I tried without success in:
ArtifactStagingDirectory
TempDirectory
StagingDirectory
Common.TestResultsDirectory
BuildDirectory

(All variables including Directory in https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml)
Thanks

Copy link

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants