tfsbuild

问题 I renamed the solution file through TFS and tried checking the code in. I keep getting this error. My best guess is that the build does not recognize that the name of the solution changed, and keeps looking for the old name. Exception Message: The file (oldName).sln could not be found. (type FileNotFoundException) Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance,

问题 I have Microsoft TFS build process to deploy web project to azure web role, this occurs automated way every day. I have followed Azure article https://azure.microsoft.com/en-in/documentation/articles/cloud-services-dotnet-continuous-delivery/ I have following MSBuild arguments in my build process, as above article suggested /t:Publish /p:PublishDir=C:\MSCD\ When i add database project to my project solution, build is keep failing. Getting error message The "SqlPublishTask" task was not given

问题 I am trying to set up Continuous Integration on Visual Studio Online, but I am getting a strange error: Exception Message: The item $/<mycollection>/Drops may not be cloaked because it does not have a mapped parent. (type WorkingFolderException) My configuration of the build item is this: The 'Build defaults' step is configured as: I must admit, that I am a bit in the blank here - what am I doing wrong? 回答1: You are getting the error as you don't have $/[collection]\drops mapped and thus can

问题 We have created a Maven project and automated test scripts using Selenium, Java and TestNG framework. The code is checked in tfs using TEE plugin and we are able to create maven build in tfs. Now we need to publish the results of the test scripts in TFS. Please advise how could we publish the results in TFS and generate reports. 回答1: Generate a custom report from TestNG is pretty easy: just implements your own IReporter . See the related documentation: http://testng.org/doc/documentation-main

问题 I have configured new build server for TFS 2015, My Xaml build runs just fine, but the vNext build always stuck with status "Waiting for an available agent." -Agent pool is Green -There is only one build agent configured -I have removed and configured the agent multiple times with no luck update 1 : **I got this from the agent log 05:20:24.283781 Sending trace output to log files: D:\Agent\_diag 05:20:24.315032 VsoAgent.exe was run with the following command line: "D:\Agent\Agent\VsoAgent.exe

问题 I'm working on a project being compiled over a TFS server. The build number format (in the process tab of the build settings) is defined as $(BuildDefinitionName)_$(BuildID) . What I can't figure out is how the $(BuildID) is incremented. If I queue, say two builds, within the same hour, it will usually increase by one, but not always. If it's been ~one week since the last build it might increment by 20 or 40. I haven't figured any pattern yet. But my real question would be : how can I make it

问题 I'm using this piece of code to determine the build definition details of a specific build: TfsTeamProjectCollection tpc = TfsTeamProjectCollectionFactory.GetTeamProjectCollection(tfsUri); IBuildServer buildServer = (IBuildServer)tpc.GetService(typeof(IBuildServer)); IBuildDetail bd = buildServer.GetBuild(buildUri); string a = bd.BuildDefinition.Name; If the tfsUri and buildUri are pointing to a TFS2013 server and a TFS2013 build then the code is ok but if I change to TFS2015 server + build

问题 I'm configuring a TFS 2015 build using the new scriptable system. During the build, when NuGet is retoring some packages, it fails with the following error: The 'System.Collections 4.0.10' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.60318.667'. The 'System.Diagnostics.Debug 4.0.10' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.60318.667'. The 'System.Globalization 4.0.10' package requires NuGet

问题 I have the following scenario: A C# Class library TFS build 2012 In the project i have the following structure: -Resources ---File.extension (type: content, copy always) When I build this localy with visual studio I get the following: bin\resources\File.extension This is what I want and expect, but on the tfs build I get the following: bin\File.extension I haven't been able to figure out why this is happening. I would like to know why this could be happening. 回答1: You can specify the Build

问题 Premise: I think this is a bug/missing functionality in TFS 2015 When I create a new Build (non-xaml) definition using the TFS website, I am not able to call it using the command line TFSBuild start command. If I create a standard XAML definition, I can start it using the command line. Any idea if the command line is not able to start a new-style definition? 回答1: The TFS Build vNext is an entirely new feature in 2015. Hence, I doubt that it can be addressed by the old API (available pre-2015)