Reputation: 883
I use VS 2013 because of Biztalk 2013 developments. Currently we use TFS 2015 with a build agent from TFS 2013 for automatic builds. We need to migrate all to TFS 2015 and we want to migrate the xaml approach of build definitions to vNext. Thing is, because of biztalk version, we need to keep using VS2013 and in the view Team Explorer under Builds I cannot see the build definitions created as vNext. I've searched for plugins/extensions and updates or even some documentation but I couldn't really find anything related to this topic.
Upvotes: 1
Views: 498
Reputation: 21
VS 2013 and lower versions do not show vNext builds and build definitions, you need VS 2015 and later for that. As an option, if you want to keep an eye on the build status, you can try CatLight build notification tool (check below 1st link) that works independently of Visual Studio and supports vNext builds. Else, Web version is pretty awesome to use and handle.
Incase you have any other queries regarding TFS builds, please let know.
Also, below Microsoft links could be helpful.
Upvotes: 2
Reputation: 30372
Just as Daniel said, the vNext build system is entirely web-based and Visual Studio 2013 does not show non-XAML build definitions.
So, you can use below workarounds to see the list of existing build definition (However you can only edit the build definitions via the web portal for vNext build definitions):
http://server:8080/tfs/Collection/Project/_build
using System;
using Microsoft.TeamFoundation.Build.WebApi;
using Microsoft.VisualStudio.Services.Client;
namespace GetBuildDefinition
{
class Program
{
static void Main(string[] args)
{
var tfsUrl = "http://server:8080/tfs/Collection";
var buildClient = new BuildHttpClient(new Uri(tfsUrl), new VssAadCredential());
var definitions = buildClient.GetDefinitionsAsync(project: "ProjectNameHere");
foreach (var definition in definitions.Result)
{
Console.WriteLine(String.Format("{0} - {1}", definition.Id, definition.Name));
}
}
}
}
Upvotes: 1
Reputation: 4119
If you have the build definitions in place and you are connected to the correct tfs workspace project, then you should see the list definition on your vs panel, the only thing that you can't do is edit the build definition. As @DanielMann said, from that point on everything is web-based, what you can do is queue a new build and see the list. You don't need any plugin for that
Upvotes: -1
Reputation: 59020
The build system in TFS 2015+ is entirely web-based. Even VS2015+ will just bounce you to the web to do anything with the builds.
So the answer is, "Get used to using the web UI."
Upvotes: 1