tfsbuild | 易学教程

Label Sources with $(GitVersion.NuGetVersion) creates Tag with variable name, not value

阅读更多关于 Label Sources with $(GitVersion.NuGetVersion) creates Tag with variable name, not value

问题 After a successful build, having configured the Label Format as $(GitVersion.NuGetVersion) , the resulting tag is set to $(GitVersion.NuGetVersion) not the actual expanded value of that variable. In the build output logging, there are 2 sections/plans: Build, and Finalize Build. Presumably, all the variable context/state is being lost once the build agent moves to the second section/plan. How am I supposed to tag the source with the resulting GitVersion if the context of the GitVersion

TFS 2010: Gated Check-In On Main Branch; Rolling Builds on Dev Branch?

阅读更多关于 TFS 2010: Gated Check-In On Main Branch; Rolling Builds on Dev Branch?

I recently migrated from VSS to TFS 2010 and I've been absolutely loving it, but there's something I haven't yet been able to get working the way I think it should. GOALS I'd like to quickly know when a change to Development breaks a build. If we find out after-the-fact, it's no big deal. Since a lot of check-ins happen throughout the day, we don't want to wait on the build to finish, so it should be asynchronous. With our Main branch, I'd like to ensure that any time a merge happens into it, we make sure it's not going to break the build. I want immediate feedback on this. The wait time is

How to build 2 solutions from a single TFS team build definition

阅读更多关于 How to build 2 solutions from a single TFS team build definition

I have a pretty large complicated application that has a smart client front end in one solution and a web services layer in another solution. We use 2 team build definitions in TFS 2010 to build the solutions. We are still using MS Build scripts not the new workflow based templates. How can we use a single build definition to build both solutions. We are open to either tricks inside MS Build scripts or moving to the new workflow templates. You can simply set two Solutions to build by creating them in an item group if I am understanding what you are trying to do <SolutionToBuild Include="$

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

Make local TFS build agent to use v14 msbuild tools

阅读更多关于 Make local TFS build agent to use v14 msbuild tools

问题 I've got a couple of ASP.NET vNext applications and I want my CI server to also be able to build them. Both my local machine and the CI server are running VS2015 RC. Then we've got VS Online and a local build controller - which is the server mentioned. However, I cannot get builds going since it seems to be looking for v12 tooling - which does not include anything DNX. So - building the solution gives: The Dnx Runtime package needs to be installed. See output window for more details It is

TFS Build 2015 not publishing test results

阅读更多关于 TFS Build 2015 not publishing test results

UPDATE (I have restructured this question with a new and basic solution and build as the same problem exists there) I'm using the new build system in Tfs 2015 and I'm using Update 1. I have noticed that on the build summary screen, no test results or Code Coverage results are submitted: I have a test step which runs and contains results and I have a .trx and a .coverage file but the test step log contains the warning: ##[warning]Failed to publish test results: The value for the Build.Id property is not within the permissible values for it. The Build is very basic, it contains 2 steps and Code

Third-party DLLs with TFS build server

阅读更多关于 Third-party DLLs with TFS build server

问题 I'm just setting up an automated build for the first time in my Team Foundation Server (TFS)/Visual Studio 2010 enviroment. It's a WPF 4 application that uses the Entprise library and has also some components that have been built in Expression Blend. The application builds OK inside Visual Studio. However, it fails to build using the build server. For example: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\Expression\Blend.NETFramework\v4.0\Microsoft.Expression.Blend.WPF

Installshield Limited Edition licencing on build server

阅读更多关于 Installshield Limited Edition licencing on build server

问题 I have recently installed Installshield LE on my local PC for vs2010, built a package and now wanting it to be built on our build server. I have also installed it on our build server. I am getting the error: error : -7159: The product license has expired or has not yet been initialized. I have logged onto the build server, started vs and entered in my licence code. However, this has has not resolved the error. I have read about the stand alone version but that appears to be only available for

TFS 2017 doesn't build Fakes targets

阅读更多关于 TFS 2017 doesn't build Fakes targets

I have a TFS 2017 Update 2 on-prem server with VS 2017 Enterprise installed. Our Build contains a Unit-Testing project which contains a Fakes assembly and works locally on the dev machines. When build on TFS, the build fails with The type or namespace name 'Fakes' does not exist in the namespace 'Our.Product' (are you missing an assembly reference?) (i.e. misses/fails to generate the Our.Product.Assembly.Fakes.dll file) I have additionally set up Fakes as suggested here . What baffles me is that there are no mentions of Fakes in the build log (except for the error itself and the paths where

How can I force exclusion of certain assemblies from Code Coverage?

阅读更多关于 How can I force exclusion of certain assemblies from Code Coverage?

问题 I'm trying to restrict the assemblies that get analyzed in the Code Coverage procedure in TFS by using a runsettings file, but some assemblies insist in being analyzed even if I exclude them explicitly. This is my current runsettings file contents: <?xml version="1.0" encoding="utf-8"?> <RunSettings>  <DataCollectionRunSettings> <DataCollectors> <DataCollector friendlyName="Code Coverage" uri="datacollector://Microsoft/CodeCoverage/2.0"