TFS 2015 - 现场构建失败 [英] TFS 2015 - On Site Build Failures

查看:22
本文介绍了TFS 2015 - 现场构建失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

背景:过去三个月内有工作过的版本.然后,在失败后,我发现许可证对于我们内部构建服务器上的 Visual Studio 安装无效.

Background: Had builds working for the past three months. Then, after getting failures I figured out the license was not valid for the Visual Studio install on our in house build server.

纠正步骤:固定许可证问题.连同安装所有 VS 更新和 TFS 更新 2.

Steps to correct: Fixed license issue. Along with installing all VS Updates and TFS Update 2.

为纠正问题而采取的其他步骤:构建仍然失败,所以我删除了代理和构建池.重新创建了一个新池并下载了代理.使用我的网络凭据在服务器上安装了代理,因为我是机器上的管理员,并且是代理池管理员和代理池服务帐户的一部分.使用我的帐户尝试消除与权限相关的问题.

Additional steps taken to correct the issue: Builds were still failing so I deleted the agent and the build pool. Recreated a new pool and downloaded the agent. Installed the agent on the server, using my network credentials as I'm an admin on the box and part of the agent pool admin and agent pool service account. Used my account to try an eliminate permission related issues.

注意:其他一切都适用于 TFS.可以签入更改,可以使用具有完全管理员权限的门户.这是日志中的最后一个条目

Note: Everything else works with TFS. Can check in changes, can use the portal with full admin rights. Here is the final entry in the logs

19:39:28.762991 无法启动作业,无法使用给定凭据创建 http 客户端.

19:39:28.762991 Failed to start the job, could not create the http client with the given credentials.

构建在一分钟内失败,tfs http 界面上没有日志或原因.

The builds fail under a minute with no logs or reason on the tfs http interface.

以下是构建服务器日志中唯一的例外情况.

19:39:18.411788 Microsoft.VisualStudio.Services.WebApi.VssServiceResponseException:错误请求

19:39:18.411788 Microsoft.VisualStudio.Services.WebApi.VssServiceResponseException: Bad Request

19:39:18.411788 在 Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponse(HttpResponseMessage response)

19:39:18.411788 at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponse(HttpResponseMessage response)

19:39:18.411788 在 Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__79.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__79.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.411788 在 Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__76`1.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__76`1.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.411788 在 Microsoft.VisualStudio.Services.Location.Client.LocationHttpClient.d__6.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.Location.Client.LocationHttpClient.d__6.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.411788 在 Microsoft.VisualStudio.Services.Client.VssServerDataProvider.d__39.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.Client.VssServerDataProvider.d__39.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.411788 在 Microsoft.TeamFoundation.DistributedTask.Agent.Common.ConnectionHelper.GetConnection(Uri serverUri, VssCredentials 凭据)

19:39:18.411788 at Microsoft.TeamFoundation.DistributedTask.Agent.Common.ConnectionHelper.GetConnection(Uri serverUri, VssCredentials credentials)

19:39:18.411788 在 Microsoft.TeamFoundation.DistributedTask.Agent.JobWriter.StartJob()19:39:18.411788 在 Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponse(HttpResponseMessage 响应)

19:39:18.411788 at Microsoft.TeamFoundation.DistributedTask.Agent.JobWriter.StartJob() 19:39:18.411788 at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponse(HttpResponseMessage response)

19:39:18.411788 在 Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__79.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__79.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.411788 在 Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__76`1.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.d__76`1.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.411788 在 Microsoft.VisualStudio.Services.Location.Client.LocationHttpClient.d__6.MoveNext()

19:39:18.411788 at Microsoft.VisualStudio.Services.Location.Client.LocationHttpClient.d__6.MoveNext()

19:39:18.411788 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.411788 --- End of stack trace from previous location where exception was thrown ---

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.411788 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.411788 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.427410 在 Microsoft.VisualStudio.Services.Client.VssServerDataProvider.d__39.MoveNext()

19:39:18.427410 at Microsoft.VisualStudio.Services.Client.VssServerDataProvider.d__39.MoveNext()

19:39:18.427410 --- 从上一个抛出异常的位置开始的堆栈跟踪结束---

19:39:18.427410 --- End of stack trace from previous location where exception was thrown ---

19:39:18.427410 在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.427410 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

19:39:18.427410 在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

19:39:18.427410 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

19:39:18.427410 在 Microsoft.TeamFoundation.DistributedTask.Agent.Common.ConnectionHelper.GetConnection(Uri serverUri, VssCredentials 凭据)

19:39:18.427410 at Microsoft.TeamFoundation.DistributedTask.Agent.Common.ConnectionHelper.GetConnection(Uri serverUri, VssCredentials credentials)

19:39:18.427410 在 Microsoft.TeamFoundation.DistributedTask.Agent.JobWriter.StartJob()19:39:18.427410 ---------------------------------------------------------------------------

19:39:18.427410 at Microsoft.TeamFoundation.DistributedTask.Agent.JobWriter.StartJob() 19:39:18.427410 ---------------------------------------------------------------------------

推荐答案

  1. 确保运行代理的帐户具有代理池服务帐户"角色.
  2. 确保在集合中配置了队列 ( https://your-tfs-server:8080/tfs/your-collection/_admin/_AgentQueue).如果不是 - 选择新队列.."并选择现有队列.
  3. 确保完全按照 这篇文章.
  4. 尝试更改属于 Build Agent Service Accounts 组成员并属于Agent Pool Service Account"角色的域帐户,以查看该代理是否有效.
  5. 检查防火墙入站规则,检查基于 TFS 2015 的 vNext 构建在 MSBuild 步骤上挂起并且不产生任何日志文件
  1. Make sure the account that the agent is run under is in the "Agent Pool Service Account" role.
  2. Make sure the queue is provisioned in the collection ( https://your-tfs-server:8080/tfs/your-collection/_admin/_AgentQueue ). If not - select "New queue.." and select the existing queue.
  3. Make sure you deploy the Windows build agent by exactly following this article.
  4. Try to change a domain account which is a member of the Build Agent Service Accounts group and belongs to "Agent Pool Service Account" role, to see whether the agent would work or not.
  5. Check the Firewall inbound rule, check vNext build on TFS 2015 hangs on MSBuild step and produces no log files

这篇关于TFS 2015 - 现场构建失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆