So I have a single Visual studio account with 3 project in it and I have three different azure subscription for deploying these projects. But I can able to link one of the subscription to VSTS. But other two are I am not able to do linking.
I did some searching on this stuff got a link saying that it is not possible : 1
So can anybody help me on this situation.
You can only link a single subscription to a VSTS account.
That is however for paying for services for VSTS. For deployment you can setup as many connections as you like on the Services tab in the administration.
You can add as many Service Endpoints as you like then use them in Tasks in both Build and Release.
Related
In order to not be restricted to 4h of build /month, in VSTS we have bought an hosted build agent for us Team (We can see it in Azure portal).
But how restrict the access to the other teams ?
In the Agent Queues i see nothing to do that...
For the same team project, you can’t do it.
For different team projects, the user with Administrator role of agent pool and project collection can create new queue. So you can remove these permissions for others and delete the Hosted queue from related team project. With this way, they can’t use Hosted queue.
BTW, there isn’t the time restrict once buy a Hosted pipeline.
Given a VS web app project that has an existing Azure publish profile is there a way to tell what subscription the selected publish profile will publish the app to? We have such so many subscriptions it's quite time consuming to to use the portals poor blade interface to locate which subscription the app is in. Even opening the SCM site it seems apps know nothing about it's subscription.
As I know, we don't need Azure subscription information to publish our project. What we need is contentPath, ComputerName, UserName& Password when you use msdeploy. The following is the parameters that used to deploy:
.\msdeploy.exe -verb:sync -source:contentPath='E:\code' -dest:contentPath='sub2',ComputerName='https://waws-prod-sn1-047.ftp.azurewebsites.windows.net/msdeploy.axd?site=sub2',UserName='$sub2',Password='key',AuthType='Basic'
If we published project to Azure, we have no easy way to see which subscription it belongs to. I suggest you submit a voice at Azure feedback forum.
I'm trying to create a build in Team Services (Visual Studio Online) but am having a few issues.
My first step is to create a new build and I've selected the template Deployment -> Azure Web App
Then in the build step for Azure Deployment I need to select my Azure subscription. This list is currently empty so I select Manage to add a new one.
Following the instructions here I try to add a new endpoint but it says to select the one called 'Azure' but in my list I've got 'Azure Classic' and 'Azure Resource Manager'. Which one should I use?
I've tried 'Azure Resource Manager' and used the details to generate service key etc using the Powershell script as said in the previous link. Now the status just stay at 'Connecting to service using Service Principal' and is not selectable in the list.
How do I get Team Services to see my Azure subscription?
I must say, I've found the documentation for this a bit lacking in that a lot of the Microsoft sites still use the classic portal or older versions for the sites.
Starting from the end of your question, one of the reasons of that is that some functionality is not available yet on the new portal. As far as i know, all of the functionality should migrate to the new portal in a future.
For Azure Web App, please add the New Service Endpoint using classic mode (and i prefer to do that using certificate - very simple). Then, when adding the web site as the build step (for example), select your added subscription and you should be good to go.
When configuring continuous deployment in Team Project with http://portal.azure.com, I receive the following error:
Unable to locate blade 'ExistingWebsitesPickerBlade' in extension
definition. Search
path:'[0]WebsitesExtension-[1]ExistingWebsitesPickerBlade'.
Any ideas?
There is nothing wrong in the process of what you are doing, but this is indeed a bug where the new portal.azure.com fails to provide you the right blade containing your existing websites to configure continous deployment.
As you can see, this is a fairly regular error that others are experiencing throughout the whole portal experience.
http://devslice.net/2015/04/azure-app-service-orchestrating-business-processes/
There might also be an issue connected to which subscription level you are currently using (ex. BizSpark, Dreamspark, Pay-as-you.go etc.) which makes the portal fail in specific areas because of the former.
Provide adequate details for your subscription level to the Azure support team (create an incident), and they are your best bet at getting through with Continuous Deployment in the new Azure portal.
I'm trying to use Set up deployment from source control to allow publishing from my TFS project to Azure, but for some reason after I authorize, it says I have no projects. The accounts are correct, I was just wondering, is there some kind of criteria for it to allow the integration or something?
I get this window
Yet I have two projects on my TFS Account.
Ended up closing my azure account and getting off of team foundation service, that solved the problem.