The new and improved XL Deploy Microsoft Team Foundation Server (TFS) plugin provides automated deployment functionality through an XL Deploy build task for Microsoft TFS 2015 and Visual Studio Team Services (VSTS) – also known as Visual Studio Online.
XL Deploy works with Continuous Integration tools to give you “one-stop-shop” deployment, so you can scale without scripting.
- Deploy complex releases at scale, more quickly and with fewer errors
- Standardize on a deployment tool for all your target platforms
- Gain visibility into deployment status of all your applications and environments
Integrating XL Deploy with TFS/ VSTS gives you one consistent way of packaging and deploying all your applications from TFS/ VSTS to all your target platforms: from your legacy enterprise apps running on on-premise middleware, to cloud, PaaS and Docker.
With XL Deploy, you have complete control and you always know what’s running where, and you can automate and scale your deployment process with much less hassle.
And now we have an even better XL Deploy plugin that is updated to work optimally with a TFS 2015 build, a.k.a build vNext. Our new plugin runs inside the latest version of TFS and VSTS, and is easier to configure and change than the old one. This new plugin allows you to build a package with TFS/VSTS, import the package into XL Deploy, and automatically trigger a deployment to your chosen environment(s). It’s easy to use – just add an XL Deploy build task to your build definition and you are ready to go.
- Create a deployment package (DAR file)
- Import a deployment package into XL Deploy
- Upload a deployment package to TFS / VSTS
- Version a deployment package
- Deploy an imported package to a specified environment
- Before you start to use the XL Deploy Microsoft Team Foundation Server (TFS) 2015 plugin, you need to upload the XL Deploy build task to your Microsoft Visual Studio Team Services (VSTS) server or on-premises Team Foundation Server.
- In Microsoft Team Foundation Server 2015 and Visual Studio Team Services, endpoints are managed in a common place. You need to create a generic endpoint for XL Deploy so that you do not have to redefine those values in every build definition that uses XL Deploy build tasks, making maintenance and credentials management easier.