Download TFS 2015 Build Agent without TFS 2015 install - xaml

We currently use TFS 2013 with a suite of XAML builds, there are a few hundred projects here, each with an average of six build definitions each.
We're wanting to upgrade to TFS 2017 (2018 doesn't support XAML) but need to be able to support the XAML builds until they're all migrated.
According to MS, we can setup a TFS 2017 box, a build server with a 2017 build agent on it and a separate build server with a 2015 build agent on it which TFS can use to run the XAML builds.
My problem is... where to get the 2015 build agent installer from. Normally you ask TFS for the build agent installer, but we don't have a TFS 2015 installation.
Am I going to have to setup a TFS 2015 VM just so I can click one lousy link and download one installer. I've searched around but can't find any other place to get the damned thing from.
Anyone got a link to an MS page?

You could download the latest build agent from the link below:
Download Latest Agent , which will download the "vsts-agent-win7-x64-2.xxx.x.zip" file for you. Currently I believe that both TFS 2015 and TFS 2017 are downloading the same latest agent as mentioned above.
If you need a specific version of the agent you could take a look at the git hub for the specific Releases of the VSTS agents

Related

VS2013 Agents from where can i download?

VS2013 agents are not found in site https://www.microsoft.com/en-hk/download/details.aspx?id=40750,where can i download it from.I want it to install in build server to run unit test from TFS xaml build.
You'll need to download the TFS 2013 ISO, run the installation, and the configure the build controller and agents.
You can find the TFS 2013 ISO by going here and then selecting "Visual Studio Team Foundation Server 2013 with Update 5".
Installation and configuration instructions can be found here.

TeamCity - 10.0.5 no compatible build agents

I'm wondering if someone could help me out with this issue please.
First up the background, we've been using TeamCity for database deployments for a while. Today we upgraded to 10.0.5. All fine.
The issue we have is with SQL 2016 database projects. I'm trying to get the database project to build in TeamCity. The build 'Visual Studio' setting in the build was set to 'Microsoft Visual Studio 2015' this causes issues as it cant build it. So I changed it to be 'Microsoft Visual Studio 2017' and I installed 'Build Tools for Visual Studio 2017' on the TeamCity box.
Now when I click the run button I get a message back saying
"Warning no enabled compatible build agents......".
Its almost as if the build agent is allowed to use the VS2015 MSBuild but not the 2017 one and I'm not sure how to authorise it to be able to.
I've attached some screenshots of the screens as well.
Thanks,
Nic
I managed to resolve this simply be restarting the server.
Thanks,
Nic

Where is the ISO for Test Agents for Visual Studio 2015?

We have TFS2015 and I am trialling Visual Studio Enterprise 2015 (no installation disk).
I am now looking for an ISO with Microsoft Test Agents for Visual Studio 2015.
Documentation for VS 2015 states that these ISOs should be available:
I can get the web installer (exe) for the Agents from here, but where can I get the ISO?
Please note: I need the ISO to get hold of Test Controller 2015 to run Load Tests, so just having the Agents is not enough.
Also, I have tried using Test Agents 2015 with Test Controller 2013, and my Agent configuration fails with a time out (whilst attempting to restart the service).
And finally, I have tried using Test Agents 2013 with TFS2015, which fails with a "Registry lookup failed" error on the "Agent Deployment" build step in our build definition (the powershell scripts used in this step assume that there is a path for an installed Test Agent 2015 in your registry). This problem is fixed by providing a path to Test Agent 2015 installer in "Test Agent Location" property of that build step.
So, I am now trying to locate the ISO with Test Agents for Visual Studio 2015 - does anybody know where I can get it from, please?
It was announced that Test Agent 2015 no longer needed a Test Controller, as the agent orchestration now is managed by the server (TFS or VSTS). You can also refer this post.
Q: Will the Test Agent 2015 support all the scenarios supported by
Test Controller and Test Agent of Visual Studio 2013?
A: We recommend you use Agents for Visual Studio 2015 in all the new automated testing scenarios. You can use the Deploy Test Agents task in a build definition to download and install the test agents on your machine. The following table shows the scenarios supported by Agents for Visual Studio 2013 and the alternatives for Team Foundation Server (TFS) 2015 and Team Services (TS).
For your situation, seems you are using on-premises Load Test , you need to use Test Controller/Test Agentes2013 Update5 . More information, please refer Using a Test Controller and Test Agents in a Load Test
As for ISO files, it seems agent for VS2013
are using the .iso including test agents and test controls in download center. But for agent for Vs2015 are just using .exe in download center.
Yes, of course, go to the page below:
https://www.visualstudio.com/vs/older-downloads/
at the scroll down the page you will see VS2015, after clicking download you will need to sign in,
then could choose the corresponding version you want to download:
do remember to sign in to Microsoft for downloading agents.
https://my.visualstudio.com/Downloads?q=Visual%20Studio%202015%20Update%203

Is it possible to add custom code coverage to TFS 2015

We use TFS 2015 vNext as our build system. However we use dotCover from JetBrains as our code coverage tool. The reason we don't use the built-in TFS code coverage tool is that this requires an Enterprise licence and we only have Professional licences (and upgrading is not an option).
Is it possible to display code coverage from a different code coverage tool to be displayed on the build results page in TFS 2015 (as in the screen shot below)?
Possible duplicate with this question Display OpenCover results in TFS 2015 build Summary .Your requirement could be achieved after TFS2015 update2.
If you want to display your custom result in the build result summary,
seems you will have to write your own extensions. Help link:
Overview of extensions for Visual Studio Team Services
Base for this were a lot of examples provided by MS on github:
Visual Studio Team Services Tasks
Visual Studio Team Services Sample Extensions
To get a first feeling what places on your TFS Web Portal can be
extended/customized you can download and install this extension
Contributions Guide from the Visual Studio Marketplace.

TFS 2013 build does not deploy ASP.NET web application

I have a new TFS 2013 instance with its own build server that compiles a solution and deploys a database project without error. I added an MS build activity for deploying the web application projects in the solution to a target server, and that activity appears to execute without error, but nothing is actually published in the target.
Running the same publish profile from within Visual Studio on my local machine works properly. I dont know if it is missing some dependency (Web deploy 3.5 is installed on both the build and target servers, I am reinstalling VS 2013 on the build server).
Are there any specific steps/prerequisites required to make this work correctly on a TFS 2013 build server? I cannot find anything on the web other than "Install VS and MSDeploy".
I have this all working properly on a 2010 build server.
After much testing and enabling diagnostic level logging, I found that the build activity was trying to use VS 2012 (version 11) activity targets for these VS 2013 (version 12) projects. (VS 2010, 2012, and 2013 have been installed on this server to support various build activities)
In the activity specific log file this looks like this...
CodeAnalysisTargets = C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\CodeAnalysis\Microsoft.CodeAnalysis.targets
This was causing the build process to log...
_DeploymentUnpublishable
Skipping unpublishable project
...and skip the publishing.
To fix this, I set the ToolVersion property of the MSBuild activity to "12.0" and re-ran the build