Deprecating XAML Builds in VSTS

Last year, I wrote a post titled Hosted XAML Builds Ending Soon. Roughly nine months has passed since that post and, as of today, Microsoft has provided a bit more detail around their plans to deprecate the XAML build functionality within VSTS. Here’s an excerpt from the post:Deprecating XAML build support in future versionsTFS – In our next major TFS release, we will take the next big step in deprecating XAML Build support.  We will remove all support for XAML builds.  We will not ship updated installers and we will remove support for connecting XAML agents/controllers.  We will also be…
Read More

VSTS Build Agent Selection Demystified

One of the (many!) features I like about Visual Studio Team Services is that, while I can create my build definitions in the cloud-hosted service, I do not have to rely on the hosted build agents to run my builds. This is important because my builds might rely on specialized software that isn’t installed on the hosted agents. It’s also possible that my build processes rely on access to other resources on my local network that is not exposed to the Internet. In the case of the company I work for, we have several on-premises build servers each running multiple…
Read More

PSA: Hosted XAML Builds Ending Soon

Earlier this year, Microsoft posted/updated some information on the Hosted Pool (i.e. where you run your automated builds in Visual Studio Team Services – i.e. VSTS). One item of interest in that post is that the hosted XAML build controller is planned to be shut down sometime next month (September, 2016).For accounts created after on or after April, 2016, access to the hosted XAML build controller was never provided, so this should not be an issue. However, if you have XAML builds running in VSTS, or were planning on migrating XAML builds to VSTS, you should take note.Here is the…
Read More

Custom Build Tasks in VSTS

[Updated 16 Jun 2016 to reflect name change from VSO to VSTS][Updated 28 Dec 2015 to reflect latest changes in command line interface]If you’ve been making use of the new Team Foundation Build technology in Visual Studio Team Services (VSTS) or Team Foundation Server (TFS) 2015 then you might have wished you had the ability to create and upload your own custom build tasks. Well, that day is now here! You can now create a custom build task and upload it to your VSTS account for use across your build definitions. Caveat The ability to upload custom tasks is still…
Read More

Why Should I Leave XAML Builds?

If you have been using Team Foundation Server for any amount of time (say, 2 years or more) then it’s likely you have a decent investment tied up in your XAML-based builds. It’s likely that you have spent a lot of time tweaking the XAML ever-so-carefully to get your automated builds to do your bidding. It’s also possible that you have utilized multiple custom build tasks for scenarios specific to your organization that are not supported out of the box.Along with this, you and/or your team has gained a good amount of knowledge in learning how to tie the various…
Read More

Custom Build Task Permissions in VSO

Following up on my Custom Build Tasks in VSO post I wanted to quickly show how you grant a VSO user permissions to upload build tasks into your VSO account. On Microsoft’s Build Tasks web page, it states that you need to be in the top level Agent Pool Administrators group to manipulate tasks. To view the Agent Pool Administrators: Sign in to your VSO account. Click on the Settings (gear) icon on the upper-right side of the page: Click on Agent pools and then Roles: Notice the Agent Pool Administrators group under Roles. This is NOT the group you…
Read More

Updating Your Team Foundation Build Agents

One of the many improvements with the new version of Team Foundation Build is the ability for the build agents to self-update. This is a HUGE time saver for anyone that has lots of build agents spread across multiple build servers! There are a couple of ways to trigger an update to your build agent(s): The build agent gets updated automatically when a build task demanding a newer version of a build agent is executed. For example, if a task demands the build agent be from sprint 84 or higher (more on that in a moment) and your build agent…
Read More