-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Using CopyFiles with CleanTargetFolder fails if the target folder does not exist #16706
Comments
Note: 2.200.0 was working for us yesterday, and today it seems that 2.208.0 is being used, so I do believe the linked PR is the root cause since the version bumped from 2.200.0 -> 2.208.0 in that PR. Successful run:
|
Thanks for working on this so quickly. Wondering about an ETA on this fix, since many of our builds are currently failing due to it. |
Confirmed this morning that 2.208.1 is pulled which contains the revert. |
@tydunkel, let me close this issue since your PR with the fix was merged |
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: CopyFilesV2
Environment
Server - Azure Pipelines
Agent - Private
Issue Description
This PR seems to have regressed using the CopyFilesV2 task with CleanTargetFolder: true when the folder doesn't exist. I believe this change is the cause since the function call switched from ignoring ENOENT to throwing.
Turning off CleanTargetFolder resolves the issue.
Task logs
The text was updated successfully, but these errors were encountered: