在 Visual Studio Team Services 路径中找不到 curl [英] curl was not found in the path Visual Studio Team Services

问题描述

我在 Visual Studio Team Services 中使用托管代理进行发布管理.我的发布定义中有一个 cURL 上传文件任务，该任务上周正在运行，并且在过去几周中我已经成功进行了几次部署.

I'm using the Hosted Agent for release management in Visual Studio Team Services. I have a cURL Upload Files task on my release definition which was working last week and I've had several successful deployments over the past weeks.

今天，我根据相同的版本定义创建了一个新版本，但在 cURL 上传文件 任务中收到以下错误.

Today I created a new release from the same release definition and I am receiving the following error on the cURL Upload Files task.

2016-03-31T08:56:43.4253012Z ##[debug]curl=null
2016-03-31T08:56:43.4263027Z ##[error]curl was not found in the path.
2016-03-31T08:56:43.4303022Z ##[debug]task result: Failed
2016-03-31T08:56:43.4313025Z Return code: 1

我检查了托管代理上的系统功能，它列出了 curl C:Program Files (x86)Gitincurl.exe 作为其中之一.

I have checked the System Capabilities on the Hosted Agent and it lists curl C:Program Files (x86)Gitincurl.exe as one of them.

有人知道为什么这突然开始失败了吗?

Any one have any ideas why this has suddenly started failing?

推荐答案

首先，很抱歉.我和产品团队在一起，我们已经确认这是我们这边的倒退.cURL 仍在框中，但已不在路径中.我们正在努力解决这个问题，但可能需要一两天的时间.与此同时，我们建议您执行以下操作:

First, sorry about this. I'm with the product team and we’ve confirmed this is a regression on our side. cURL is still on the box but it is no longer in the path. We’re working on getting this fixed on our end but it’ll likely take a day or two. In the meantime, we’d recommend doing the following:

1. 在执行 curl 任务之前，创建一个新的 powershell 任务
2. 将任务的类型更改为内联脚本"
3. 将内联脚本输入更改为以下内容:

echo "##vso[task.setvariable variable=PATH;]$env:PATH;C:Program FilesGitusrin"

1. 保存新构建并将其加入队列.

<小时>

更新:我们现在已经解决了这个问题.应该不再需要该解决方法.

---

UPDATE: We've fixed this issue now. The workaround should be no longer necessary.

这篇关于在 Visual Studio Team Services 路径中找不到 curl的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！