team-build | 易学教程

Adding parameter to “Queue New Build” Dialog

阅读更多关于 Adding parameter to “Queue New Build” Dialog

问题 I built a custom build processes template based on the DefaultTemplate.xaml and added a few parameters. They show up fine on the Build definition window but I can not find a way to have them be displayed on the parameters tab of the Queue New Build Dialog. I am hoping that this is possible, I would rather not need to define a separate build for each variation of parameters. 回答1: You can define that in the Metadata parameter: http://www.ewaldhofman.nl/post/2010/05/17/Customize-Team-Build-2010

Is there a .NET API equivalent to the “Build 2.0” REST API for TFS 2015?

阅读更多关于 Is there a .NET API equivalent to the “Build 2.0” REST API for TFS 2015?

问题 The REST API Reference for VS Team Services and TFS page separates the "Build 1.0" and "Build 2.0" APIs. It seems like such a difference also exists in the .NET API because running the following code only lists the "old" XAML build definitions and not the new ones. var tpc = new TfsTeamProjectCollection(new Uri("http://tfsurl")); var buildServer = tpc.GetService<IBuildServer>(); var def = buildServer.QueryBuildDefinitions("Project Name"); // Finds only XAML definitions Is there a new DLL I

Problem with Team Build 2010 and web.config transformation

阅读更多关于 Problem with Team Build 2010 and web.config transformation

问题 I'm struggling to get web.config transformations working with automated builds. We have a reasonably large solution, containing one ASP.NET web application and eight class libraries. We have three developers working on the project and, up to now, each has "published" the solution to a local folder then used file copy to deploy to a test server. I'm trying to put an automated build/deploy solution in place using TFS 2010. I created a build definition and added a call to msdeploy.exe in the

Release Management sets builds to Retain Indefinitely

阅读更多关于 Release Management sets builds to Retain Indefinitely

We are using Microsoft's Release Management tool for automating the deployment of our solution to our various dev servers. This tool is ideal for us because it can perform more complicated deployments that span multiple servers. In this sense, it is working fine and everything is deploying correctly. A minor issue is that after Release Management automatically deploys a build, it sets the build to "Retain Indefinitely" which is indicated by the Lock icon. Since we are doing continuous deployment, we are retaining a large number of builds and the Build Definition's retention policy is

TFS: Building solutions with multiple configurations

阅读更多关于 TFS: Building solutions with multiple configurations

问题 Scenario: On TFS 2013, I have to build 300+ projects (C# and VC++), divided among, around 40 solutions. Some projects have multiple Release and Debug configurations e.g one project may have 3 Release configurations like Release 1, Release 2, Release 3|x86, Release 4|x64 etc. Requirement: I'm trying to find TFS feature to build a solution with Release configuration, it should detect all the Release Configurations specified in projects added to that solution, and build all configurations. (Same

WebDeploy to deploy multiple web sites

阅读更多关于 WebDeploy to deploy multiple web sites

问题 We're using this process to use WebDeploy to deploy and compile two web sites that are a part of the solution. The approach we took was found here: http://vishaljoshi.blogspot.com/2010/11/team-build-web-deployment-web-deploy-vs.html But it's only deploying one of the web sites; is there a way to tell it to publish both? Thanks. 回答1: Web Packages created based on the above walkthrough (i.e. via VS 2010 and its derivatives like TFS etc) can only contain one web project. Unfortunately VS

TFS 2010 API - Get work items from merge

阅读更多关于 TFS 2010 API - Get work items from merge

I need to send an email on completion of a build in TFS 2010 which details the work items associated with check-ins that have been compiled as part of this build. This works no problem via use of the associatedChangesets variable available in the build workflow. However, in a production situation, we will merge changes from our Development branch into a Release branch. At this point, the build considers there to have only been one change - which is the aforementioned merging of Development into Release. Obviously this is fairly useless as we need to find out which changes where made in the

Team Build: The path 'Path' is already mapped in workspace 'workspace' error even after deleting all workspaces on build agent

阅读更多关于 Team Build: The path 'Path' is already mapped in workspace 'workspace' error even after deleting all workspaces on build agent

问题 I have this problem when I queue a build. The build dies with the error The path C:\[Path]\Sources is already mapped in workspace [Server Name]. the same as this question. but I've removed all the workspaces on the build agent by running this command: tf workspaces /remove:* and also by deleting the TFS cache folder. I've also restarted the server, but the error keeps happening on each build. 回答1: Ok, so the solution ended up being fairly similar to what YeahStu posted on here. I changed the

How can one determine if a csproj is being run on a TFS build agent?

阅读更多关于 How can one determine if a csproj is being run on a TFS build agent?

We use TFS 2010. There are a couple of projects with deployment steps which must know whether they are running on a dev machine or on the TFS build agent. Right now they check whether the build is from within Visual Studio assuming that only devs compile from VS. Alas, it means I cannot compile from the command line! So, my question is how an msbuild script can determine if it is being run by the TFS build agent? You have a few options: '$(BuildingInsideVisualStudio)' != '' '$(TeamBuildConstants)' != '' (supported in team Build 2008) '$(IsDesktopBuild)' == 'false' You can check either one to

Is there a .NET API equivalent to the “Build 2.0” REST API for TFS 2015?

阅读更多关于 Is there a .NET API equivalent to the “Build 2.0” REST API for TFS 2015?

The REST API Reference for VS Team Services and TFS page separates the "Build 1.0" and "Build 2.0" APIs. It seems like such a difference also exists in the .NET API because running the following code only lists the "old" XAML build definitions and not the new ones. var tpc = new TfsTeamProjectCollection(new Uri("http://tfsurl")); var buildServer = tpc.GetService<IBuildServer>(); var def = buildServer.QueryBuildDefinitions("Project Name"); // Finds only XAML definitions Is there a new DLL I can reference to write equivalent code that will work with the new TFS or is the web API all there is?