tfsbuild

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 installed - since it came with VS2015 RC, AFAIK. So I thought the build template isn't using v14 tooling.

Trying to set up build server after upgrading to TFS 2015. The way I envision is: Single Agent Pool, that will have 3 queues: 1. Nightly builds 2. CI builds 3. Gated/validation builds. Each of them will have some agents, the goal is to have some control, to make sure nightly builds wouldn't consume all agent, so gated queue will always have some available agent. The problem I have now is when I try to add new queue, the option "Use existing pool" is disabled, I can only add queue with creating new agent pool. It doesn't work the way you want it to work. One agent can be a member of one and

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 variables are lost during the Finalize Build section? https://github.com/Microsoft/vsts-agent/issues/716 I

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

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.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file

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 premium edition. Anyone have any ideas? FlyerMM if you are using the 2012 Spring edition of

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> <!-- Configurations for data collectors --> <DataCollectionRunSettings> <DataCollectors> <DataCollector friendlyName="Code Coverage" uri="datacollector://Microsoft/CodeCoverage/2.0" assemblyQualifiedName="Microsoft.VisualStudio.Coverage.DynamicCoverageDataCollector, Microsoft.VisualStudio

Has anyone attempted to integrate jest unit tests with TFS 2015? I tried to use Chutzpah Test Adapter ( https://visualstudiogallery.msdn.microsoft.com/f8741f04-bae4-4900-81c7-7c9bfb9ed1fe?SRC=VSIDE ) however it's not able to recognize jest. I receive below error: Can't find variable Jest When I run the unit tests through "npm test" I get the results. However to integrate with TFS 2015 I need a test runner which can run Jest unit test so that I can run the unit tests in conjunction with vstest.console.exe which the TFS 2015 provides so it can manage build results and publish results in the