You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agent - Private Windows agent, agent version 2.165.0
Issue Description
If you are downloading a pipeline artifact (from another pipeline) and the name of the artifact is used in the folder structure of the artifact, it can cause the following issues.
So it seems that the 'artifact name' is deleted from the folder structure, which may result in lost folder-levels or changed folder names and changed file names. And the breaking only happens for only the folder that has similarities with the artifact name, rest of the folders stay as they should. Also if you check the built artifact, there the folder structure is correct. So the copying breaks it.
Task logs
No logs, just observed functionality from the result.
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
I have experienced this bug today. One of the folders has the same name as the generated artifact, and when it is downloaded the folder just disappears.
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: DownloadPipelineArtifact@2
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment
Server - Azure Pipelines
Agent - Private Windows agent, agent version 2.165.0
Issue Description
If you are downloading a pipeline artifact (from another pipeline) and the name of the artifact is used in the folder structure of the artifact, it can cause the following issues.
Folder level removed, file renamed:
Solutions/ThisIsAnArtifactName/url.runsettings
-> Solutions/ThisIsAnurl.runsettings
Folder level removed:
Solutions/ThisIsAnArtifactName/Obj/...
-> Solutions/ThisIsAnObj/...
So it seems that the 'artifact name' is deleted from the folder structure, which may result in lost folder-levels or changed folder names and changed file names. And the breaking only happens for only the folder that has similarities with the artifact name, rest of the folders stay as they should. Also if you check the built artifact, there the folder structure is correct. So the copying breaks it.
Task logs
No logs, just observed functionality from the result.
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
No logs, just observed functionality from the result.
The text was updated successfully, but these errors were encountered: