成功构建后,“集成在构建”字段未在Bug工作项中更新 [英] 'Integrated In build' field is not getting updated in Bug work item after successful build

查看:85
本文介绍了成功构建后,“集成在构建”字段未在Bug工作项中更新的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Hello Team,

Hello Team,

我们正在使用TFS 2015 vNext版本,并且每当构建失败时都会尝试创建错误,并将它们与下一个成功构建相关联。我们按照下面博客中提到的所有步骤进行了操作,但不知怎的,它正在捕获异常,并尝试执行
语句中"catch"部分中提到的任何内容。当试图明确地运行时,我知道它没有采用PS脚本中定义的$ env变量。能帮助我们实现我们想要的目标吗?

We are using TFS 2015 vNext builds and are trying to created bugs whenever builds fail and associate them with the next successful build. We followed all the steps mentioned in the below blog but somehow it's catching the exception and trying to execute the statement whatever mentioned in the 'catch' section. When tried to run explicitly, I got to know that it's not taking $env variables defined in the PS script. Could you please help us in achieving what we are looking for?

https://blogs.msdn.microsoft.com/tfssetup/2016/05/09/build-association-with- work-item-in-vnext /

https://blogs.msdn.microsoft.com/tfssetup/2016/05/09/build-association-with-work-items-in-vnext/




谢谢,

Ashish

推荐答案

您好Ashish,

Hi Ashish,

感谢您在此发帖。

  在我这边检查,可以重现这个问题。 powershell可以成功执行,但没有与成功构建相关联的工作项。

I  checked at my side and can reproduce this issue. The powershell can be executed successfully but no work items associated with the successed build.

看起来脚本有问题。它需要首先找到最后一个失败的构建ID然后获取相关的bug,然后将'Microsoft.VSTS.Build.IntegrationBuild'值更改为当前构建号。

Seems something wrong with the script. It needs to find the last failed build id first then get the associated bug, then change the ‘Microsoft.VSTS.Build.IntegrationBuild’ value to current build number.

发布的powershell脚本只是尝试获取当前的构建ID并检查相关的工作项。原因没有结果。

The posted powershell script just try to get current build ID and check the associated work items. Of cause no result.

请参考这些主题:

最好的问候。


这篇关于成功构建后,“集成在构建”字段未在Bug工作项中更新的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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