当我从TFS触发构建以通过发布管理(又称发布)进行部署时,我收到如下所述的错误.
*错误*
The account running the TFS build service (TFSBuildServices) needs to be added as a system user in the Release Management Server. at Microsoft.TeamFoundation.Release.Workflow.Services.ReleaseWorkflowService.InitiateFromBuild(String teamFoundationServerUrl, String teamProject, String buildDefinition, String buildNumber, String targetStageName) at Microsoft.TeamFoundation.Release.Build.Program.Release() at Microsoft.TeamFoundation.Release.Build.Program.Main()**
我使用的模板是 ReleaseDefaultTemplate.11.1.xaml
任何帮助将非常感激.
谢谢!!
--Update--
下面是Build Server上生成的日志
"C:\用户\ TFSBuildServices \应用程序数据\本地的\ Temp \微软\ ReleaseManagement\12.0 \日志\ ReleaseManagementBuild.log"
1/7/2014 3:04:14 PM - Error - Error loading profile for current user: ***\tfsbuildservices 1/7/2014 3:04:14 PM - Error - Unable to connect to the remote server: \r\n\r\n at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.TeamFoundation.Release.Data.ConfigurationServiceRef.ConfigurationService.GetUserByUserName(String userName) at Microsoft.TeamFoundation.Release.Data.Model.CurrentUser.get_Profile() 1/7/2014 3:04:14 PM - Error - No connection could be made because the target machine actively refused it 127.0.0.1:29622: \r\n\r\n at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
@Update With Solution
感谢大家的帮助来解决这个问题.
该代理在Buildserver是罪魁祸首.这是为服务帐户tfsbuildservices 启用的.由于它总是遇到错误的RM服务器(本地地址错误的端口).
后禁用的代理在构建服务器帐户tfsbuildservices,它开始工作正常.谢谢!!
在发布管理客户端中,添加与帐户TFSBuildServices匹配的新用户.设置'是服务用户吗?' 字段是的.
UPDATE
根据您添加的其他日志,问题似乎与Build Server框上安装的RM客户端的配置有关.
打开Build Server框上安装的客户端,您应该弹出一个窗口来配置指向RM Server的URL.一旦您能够打开客户端,请尝试触发新的构建.