Service endpoints – Data sources

Specifying data sources Overview Service endpoints support querying data from external services through REST API. The data queried can be used to populate task input dropdowns. Endpoints can define data sources which are essentially external service’s REST API references. For e.g. Azure RM endpoint type defines the following data source: { “name”: “AzureRMWebAppSlotsId”, “endpointUrl”: “$(endpoint.subscriptionId)/resourceGroups/$(ResourceGroupName)/providers/Microsoft.Web/sites/$(WebAppName)/slots?api-version=2015-08-01”,…


Service endpoints – Customization

Customizing service endpoints Overview Basic goal for customizing service endpoint is to allow extensibility of endpoint type. This extensibility serves the following purposes: Choosing appropriate authentication scheme(s) for the endpoint type. Inputs/URL for the endpoint type can be customized to help user when creating endpoint. Custom icon for the endpoint type can be provided to…


Service endpoints – Authentication schemes

Authentication scheme in a service endpoint determines the credentials that would be used to connect to the external service. In order to populate task drop downs, TFS/VSTS connects to the external service using the credentials provided as part of the endpoint. TFS/VSTS effectively becomes a client of the external service querying for details pertaining to…


Service endpoints – Overview

Purpose TFS/VSTS supports Continuous Integration (CI) & Continuous Deployment (CD) scenarios involving external services: Building source code from various external source repo providers like GitHub, SVN etc. Consuming build artifacts from various external services like Jenkins, TeamCity etc. within release. Deploying applications to various external services like Azure, Chef, SCVMM, Docker etc. as part of…


Hello world!

Welcome to Developer Network. This is your first post. Edit or delete it, then start blogging!