2017-06-29 32 views
0

我正在使用Team Foundation Server 2017更新1. 我创建了一个发布管理,其中包含工件之间的XAML构建,与发布定义不一样。 每当我运行发行版时,我都会在下载那个工件时失败。 我试图使用来自位于同一个项目中的不同版本管理的相同版本,以及来自不同项目的其他vNext版本,并且在这两种情况下都可以下载。TFS2017 - 构建和发布管理 - 从不同项目下载XAML构建工件时出错

这里的日志中的错误的下面:

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

完全有可能您尝试的方案不受支持 - XAML构建已弃用。 –

+0

在发行版定义中,我遇到了另一个xaml版本问题,它在与发布定义相同的项目中定义,并且工作正常。 –

+0

Right。这个场景是“我想从跨团队项目边界的发布定义访问XAML构建。”这可能是不受支持的情况。 –

回答

0

的问题是在2017年TFS 2017年更新2

有关的bug

的更多信息,可以发现here一个bug已被固定在TFS:

为了解决这个问题,你必须更新TFS代理人版本2.117.2。

0

经过更多的细节和测试后,得到了和你一样的结果和错误信息。 “整个团队项目”场景中没有针对XAML构建的额外设置。

Noticed you have also submitted a bug to DeveloperCommunity-TFS-- Error downloading artifacts of XAML build from different project

这是直接向TFS团队提交bug的正确位置,开发人员和PM会及时跟进。你只需要关注该网站。

恐怕这很可能是XAML构建时不支持的情况。此外,丹尼尔是正确的XAML构建是一个遗留构建系统,并已过时。强烈建议您移动基于新任务的系统。

+0

嗨帕特里克,感谢您的帮助,不幸我已经试图通过web api查看构建,并且我看到构建是在我放入正确的项目时发现的,当我将构建所在的项目(显然:))。不幸的是,失败的函数不是我开发的代码,而是微软的代码。 –

+0

@MattiaMagosso通过更多的细节和测试后,得到了和你一样的结果和错误信息。 “整个团队项目”场景中没有针对XAML构建的额外设置。 注意到您还提交了一个bug到 ** DeveloperCommunity-TFS **。它是直接向TFS团队提交bug的正确位置,开发人员和PM将及时跟进。你只需要关注该网站。更多细节请看我的更新答案。 –