Delete process

When you delete a build number, follow these steps:

• Verify that the build number is valid and the build is not in progress.

• Delete the contents of the build store and drop site if the requestor has Administer Build permission.

• Clear the drop location of the binaries from this build. If a failure occurs during this process, you are prompted with a warning message. However, even with the warning, the deletion is considered successful.

  Note:
  No data is deleted from the warehouse.

Multiple builds being deleted

If you specify multiple builds, a failure in deleting one of the builds does not stop the process. The command continues deleting the other builds after providing a build-deletion-failure error message.

Event log

Build deletions are logged in the event log. The log will have information about who deleted the build, the time the build was deleted, and the build number.

The following example deletes two builds defined by build numbers "TestBuild1 1_20070510.1" and "TestBuild 1_20070510.2" from the AdventureWorks team project on server01.

> > tfsbuild.exe delete http://server01:8080 Adventureworks “TestBuild1 1_20070510.1” “TestBuild 1_20070510.2”

The following example deletes two specific builds where the definitionSpec is "\Adventureworks\Definition1" from the AdventureWorks team project on server01.

>tfsbuild.exe delete /server:http://server01:8080 /builddefinition:”\Adventureworks\Definition 1” “Definition 1_20070510.1” “Definition 1_20070510.2”

The following example deletes two builds defined by the build URIs "vstfs:///TestBuild/TestBuild/1" and "vstfs:///TestBuild/TestBuild/2" from the AdventureWorks team project on server01.

>tfsbuild.exe delete /server:http://server01:8080 vstfs:///TestBuild/TestBuild/1 vstfs:///TestBuild/TestBuild/29

Tasks

Other Resources