我正在使用Team Foundation Server 2017 Update 1。 我创建了一个发布管理,它在其工件中包含一个项目的XAML构建,该项目与发布定义不同。 每当我运行该版本时,我都无法下载该工件。 我尝试使用位于构建的同一项目中的不同版本管理中的相同构建以及来自不同项目的其他vNext构建,并且在下载情况下都可以使用。
下面是错误日志:
An error occurred during download: System.AggregateException: One or more errors occurred. ---> Microsoft.TeamFoundation.Build.WebApi.BuildNotFoundException: Requested build 34588 could not be found.
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponse(HttpResponseMessage response)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__46.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__27`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__26`1.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Microsoft.TeamFoundation.Release.ArtifactRepository.Build.BuildArtifact.EnsureVersionBelongsToLinkedDefinition(ArtifactDefinition artifactDefinition, BuildHttpClient buildClient, XamlBuildHttpClient xamlBuildClient)
at Microsoft.TeamFoundation.Release.ArtifactRepository.Build.BuildArtifact.Download(ArtifactDefinition artifactDefinition, String localFolderPath)
at Microsoft.TeamFoundation.DistributedTask.Plugin.Release.AgentArtifactDownloader.Download(ArtifactDefinition artifactDefinition, Uri workingFolder)
at Microsoft.TeamFoundation.DistributedTask.Plugin.Release.ReleaseJobExtension.<>c__DisplayClass23_0.<DownloadArtifacts>b__1()
at Microsoft.TeamFoundation.Release.Windows.Implementation.RetryExecutor.Execute(Action action)
---> (Inner Exception #0) Microsoft.TeamFoundation.Build.WebApi.BuildNotFoundException: Requested build 34588 could not be found.
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.HandleResponse(HttpResponseMessage response)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__46.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__43`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__27`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.<SendAsync>d__26`1.MoveNext()<---
有没有人看到类似的东西,并知道如何解决它?
答案 0 :(得分:0)
在完成更多细节和测试后,得到与您相同的结果和错误信息。 在团队项目中没有额外的XAML构建设置&#34;场景。
注意到您还提交了一个错误 的 DeveloperCommunity-TFS 强> - Error downloading artifacts of XAML build from different project
它是直接向TFS团队提交错误的正确位置,开发人员和PM将及时跟进。你只需要关注那个网站。
我担心这可能是XAML构建的一个不受支持的场景,概率很高。此外, Daniel 是正确的XAML构建是遗留构建系统,不推荐使用。强烈建议您移动基于任务的新系统。
答案 1 :(得分:0)