TF42064: The build number already exists for build definition error in TFS2010

In TFS2008, deleting a build removes it from the database itself. If you delete a build called Build_20110423.1 or 1.0.0.1 from Build Explorer and trigger the build again then you will see that new builds starts with same number (Build_20110423.1 or 1.0.0.1) but not with an incremental number (Build_20110423.2 or 1.0.0.2). But, it doesn’t work the same way in TFS2010.

I queued a build in TFS2010 which got failed with Build Number 1.0.14.0 due to compilation errors.

I wanted to reuse the same build number. So, I have deleted the Build from Build Explorer by checking all the available options.

Triggered the Build again but it got failed with error TF42064: The build number ‘1.0.14.0’ already exists for build definition.

This is because in TFS2010 when you delete the builds, it only gets marked as deleted in the database so that it doesn’t show up in the UI anymore. To get rid of this build completely you actually have to Destroy it using tfsbuild destroy command which is added in TFS2010.

Open the Visual Studio Command Prompt and you can run the tfsbuild destroy command in below mentioned syntax.

C:\WINDOWS\system32>tfsbuild destroy /collection:http://TFSServer:8080/tfs/defaultcollection /builddefinition:"TeamProject\BuildDefinitionName" BuildNumber 1.0.14.0

No builds found for build specification ‘BuildNumber‘.
Destroy build record for 1.0.14.0 permanently? (Yes/No/All) yes
Destroying 1.0.14.0... Done

I queued the build again and now the build succeeded with 1.0.14.0 Build Number.

时间： 2024-12-14 18:48:20

TF42064: The build number already exists for build definition error in TFS2010的相关文章

Errors occurred during the build. Errors occurred during the build. Errors running builder 'JavaScript Validator' on XXX

选择项目--右键Properties--Builders--如果有则取消第一项“JavaScript Validator”的勾. http://blog.csdn.net/error_case/article/details/21369337 Errors occurred during the build. Errors occurred during the build. Errors running builder 'JavaScript Validator' on XXX

Eclipse项目导入Android Stuio 配置出现 Timeout waiting to lock buildscript class cache for build file 'H:\studioproject\Generic_SN\build.gradle'

Eclipse项目导入Android Stuio 配置出现 Error:Timeout waiting to lock buildscript class cache for build file 'H:\studioproject\Generic_SN\build.gradle' (C:\Users\Administrator\.gradle\caches\2.2.1\scripts\build_81ep6udn3nlzszbotl32uedjz\ProjectScript\buildscri

Build step ‘Execute shell‘ marked build as failure

shell 脚本远程调用执行如下:/usr/bin/ssh 10.1.2.3 '/bin/bash /root/ReServer.sh'报错如下:Build step 'Execute shell' marked build as failure 本地执行是ok,怎么执行都报错,后来折腾了老半天,一步一步的打输出,发现:原来是脚本在判断进程是否存在的同时,这个结束进程刚好有同样的匹配串!ps -aux | grep "idiot" | grep -v grep | grep -v '$

Ex2010-06 Get version number, build number

http://exchangeblog.pl/en/2012/10/exchange-2010-get-version-number-build-number/ http://exchangeblog.pl/en/microsoft-exchange-build-numbers/ http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-build-number

Win10 Build 9860升级到版本号Build 9860

昨天迎来了win10 更新,但有非常多人点更新后且没升级到Build 9860,那是怎么回事呢.如今小编来说下我的方法. Win+I:打开Charm栏→设置菜单.点击"更改电脑设置" 在按下图点击升级: 好了

Bentley LumenRT 2015.5 Build 2015502058 Win64+Perla Premium Build 2754

Bentley LumenRT 2015.5 Build 2015502058 Win64 1DVD Mentor Graphics Calibre 2015.1 Linux 1DVD Perla Premium Build 2754 1CD CAE辅助分析的Enmesh GoSimulate v1.4.1Enmesh GoSimulate v1.4.1是一款通过综合传热和应力计算到设计过程的方式的革命性的设计软件,具有快速 .方便和直观等特点. Enmesh GoSimulate改变了你的设计

Win10 Build 9860升级到版本Build 9860

昨天迎来了win10 更新,但有很多人点更新后且没升级到Build 9860,那是怎么回事呢.现在小编来说下我的方法. Win+I:打开Charm栏→设置菜单.点击"更改电脑设置" 在按下图点击升级: 好了

nuxt build 项目文件分析、nuxt build 发布后的资源如何部署cdn

建议在项目发布的时候,还是将.nuxt 进行发布到生产环境,是比较稳妥的做法 出处:https://nickfu.com/p/150 nuxt build 后的前端资源都会存放在.nuxt/dist/ 文件夹下面 出处:https://nickfu.com/p/139 原文地址:https://www.cnblogs.com/cag2050/p/11122962.html

uva 1151 - Buy or Build poj 2784 Buy or Build（最小生成树）

也是简单的最小生成树算法 不过添加了一些新的东西,需要对最小生成树算法 以及其中的 并查集的使用 有一些比较深入的理解. 处理问题的方法也有些复杂 #include<cstdio> #include<cstring> #include<vector> #include<algorithm> using namespace std; const int maxn = 1005; struct point { int x; int y; }pp[maxn]; s