VSO复制到任务失败，原因不明 [英] VSO copy to task is failing for unknown reason

问题描述

我有一个Visual Studio团队服务构建设置.到目前为止，我有2个步骤.

I have a visual studio team services build setup. I have 2 steps so far.

Visual Studio Build-这很漂亮复制文件-这也取决于我在哪里设置目标路径.

Visual Studio Build - this works beautifully Copy files - this works depending on where I set the target path too.

现在，我需要将输出的文件部署到我们的应用程序中.有多个任务要使用:复制文件，复制和发布构建工件，发布构建工件等.

Now I need the outputted files to be deployed to our application. There are multiple tasks to use: copy files, copy and publish build artifacts, publish build artifacts, etc.

我决定复制文件，因为这似乎是最直接的方法，毕竟，我只需要复制文件.:)

I decided on copy files because it seemed the most straight forward, and after all, I just need to copy files. :)

我的问题是，如果我将目标文件夹更改为E:\ test \，它将复制所有内容.但是，将目标文件夹设置为应用程序路径:E:\ Program Files \ App \ CI我收到以下错误消息:

My issue is that if I change the target folder to E:\test\ it copies everything wonderfully. However with the target folder set to the application path: E:\Program Files\App\CI I get the following error message:

******************************************************************************
Starting task: Copy Files to: E:\Program Files\App\CI
******************************************************************************
Set workingFolder to default: E:\build\agent\tasks\CopyFiles\1.0.9
found 65 files
shell.js: internal error
Error: ENOENT, no such file or directory 'E:\build\agent\tasks\CopyFiles\1.0.9\"E:'
    at Error (native)
    at Object.fs.mkdirSync (fs.js:747:18)
    at mkdirSyncRecursive (E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:11:8)
    at mkdirSyncRecursive (E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:16:3)
    at mkdirSyncRecursive (E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:16:3)
    at mkdirSyncRecursive (E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:16:3)
    at mkdirSyncRecursive (E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:16:3)
    at E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:63:7
    at Array.forEach (native)
    at Object._mkdir (E:\build\agent\tasks\CopyFiles\1.0.9\node_modules\shelljs\src\mkdir.js:48:8)
******************************************************************************
Finishing task: CopyFiles
******************************************************************************
System.Exception: Task CopyFiles failed. This caused the job to fail. Look at the logs for the task for more details.
at Microsoft.TeamFoundation.DistributedTask.Worker.JobRunner.Run(IJobContext jobContext, IJobRequest job, IJobExtension jobExtension, CancellationTokenSource tokenSource)
Worker Worker-56b6a6c0-8c1d-4dc3-b200-385e5c7a7625 finished running job 56b6a6c0-8c1d-4dc3-b200-385e5c7a7625

在错误中显示:

错误:ENOENT，没有这样的文件或目录'E:\ build \ agent \ tasks \ CopyFiles \ 1.0.9 \"E:'

Error: ENOENT, no such file or directory 'E:\build\agent\tasks\CopyFiles\1.0.9\"E:'

结尾的"E:跳到我身上，但是不确定为什么要这么做.对此有什么想法吗?

The trailing "E: jumps out at me, but am not sure why it's doing that. Any thoughts on this?

推荐答案

我最后一次看到复制文件"任务的问题是，我在目标文件夹"路径的开头输入了一个多余的空格.我只是再次尝试了一次，输入空格仍然会出现相同的错误.因此，您可能需要检查一下，然后再次尝试构建.

The last time I see this issue with "Copy Files" task is that I entered a redundant blank space at the begin of the Target Folder path. I just tried it again and can still get the same error with the blank space enter. So you may need to check this and then try build again.

这篇关于VSO复制到任务失败，原因不明的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！