We've been able to setup Azure Continuous Deployment with some VSO Team Projects, but not others. Any idea why we are getting this error in the Azure Management Portal? Perhaps it depends on the age of the team project.
Unable to find AzureContinuousDeployment.11.xaml in TeamProject see [Link]
We've followed the directions suggested:
Integrating Azure Continuous Integration with VSO
Add Build Template AzureContinuousDeployment.11.xaml to $/[TeamProject]/BuildProcessTemplate
Created Build Definition in [TeamProject] referencing AzureContinuousDeployment.11.xaml in Step 1 (i.e. Registering the Template)
Proceed with "Set up publishing with Visual Studio Online". Enter VSO host and select [TeamProject].
I can see there are connected services under the [Team Project] in VSO (under Team Project Admin -> Services).
Turns out the Azure Portal/VSO error message needs updated to reflect new Azure Continuous Deployment updates for TFS 2013 (Microsoft.TeamFoundation.Build.Client).
Proper Error Message
Unable to find TfvcContinuousDeploymentTemplate.12.xaml in [TeamProject] see [Link]
The fix is to upload the TFS 2013 Azure CD template and create a build definition to register the template with the [TeamProject].
This is only necessary for older VSO projects that don't get the default Azure CD build template.
Related
I am trying to create a new Release definition for deploying one of the web app I have in Visual Studio online team project. When I authorize the Azure subscription it gives me an error:
Error(s):
Session Id: 0c6e8341-1119-44fc-a70f-5f4cef94aa80
I have a free trial subscription with Azure and my build releases stopped working because of :
XAML build based TFS deployments are deprecated in Azure and have been replaced by DevOps tools in Visual Studio Team Services to build, test, and deploy with Continuous integration and Continuous delivery pipelines. Starting on November 1st, 2016, you will no longer be able to view your deployments from portal.azure.com and will instead need to use your visualstudio.com account portal once you have migrated to the new system. To perform the migration, you must:
Login to your Visual Studio Team Services project at visualstudio.com and add a new pipeline for continuous deployment
Return to this page and click the 'unlink' button to complete the process.
Note: Once you have 'unlinked', you will no longer be able to set up XAML build based TFS deployments. Learn more
Thanks.
You would need to do the following below.
1. Click on Manage button next to the Authorize button.
2. Create and Add the endpoint or XAML build Services(based on your code) for your Azure subscription
2. Point the release to that endpoint
Thanks
I have set up Azure continuous deployment from a branch in my Visual Studio Team Services GIT Repository. Everything is working fine however I would like to run a few gulp tasks before the actual deployment takes place. Is there a way how I can do this?
Azure provides continuous deployment out of the box through the use of several sources of your code. What you will need will be more in the side of continuous integration, running tasks and flows to build the code.
There are many ways and tools of doing continuous integration, nevertheless the most compatible to do this in Azure would be within the build and release parts of Visual Studio Team Services.
Within your Azure subscription you can setup this following the next steps(it seems you have already setup your code in Visual Studio team services, then you can skip to step 3):
Creating a VSTS project
Putting your code in a Git Repo inside VSTS
Creating a Build definition
Adding your tasks from the Catalog
Adding and configuring your Gulp Tasks
Deploying the build to Azure
I used Visual Studio Team Services for deployment of an MVC website on azure and it was successful.
I also created deployment slots.
Now I would like to rollback the deployment, but I am unable to find the Active Deployment blade on portal.azure.com.
Update 1:
I went to Deployment Source>Choose Source>Visual Studio Team Service> Choose a project. When I clicked it, it did not show any project, although I have project on my Visual Studio Team Services.
I did it other way. I went to Visual Studio Team Services, and there established trust relationship between Azure and Team Services. I succeeded with deployment.
Two things need to be checked:
Check whether you have linked a VSTS:
Check whether your team projects are using Git version control. When you select "Visual Studio Team Services" as deployment source from New Azure Portal, it is using Kudu service which is designed for Git version control. So it will only show the projects with "Git" repositories.
If you want to deploy the TFVC project, try with Azure Classic Portal.
You can refer to this article for details: Continuous delivery to
Azure using Visual Studio Team Services
Am trying to setup deployment from source control for Azure App Service. Am facing errors in the same. The error that am receiving is:
Cannot create build definition as no hosted build controller could be found.
Am trying to configure this via "Visual Studio Online" option by clicking "Setup deployment from source control" in a slot of Azure App Service.
There are two issues in your question:
For the New Portal, it can only show the projects with Git Version Control. If you project is using Team Foundation Version Control(TFVC), it cannot be listed. You can refer to this question for deteails: Azure Functions deployment source Visual Studio Team Service project.
For the Classic Portal, I can get the same issue with you and it is caused by the failure when create a XAML build definition. When you create a XAML build definition from VS directly, you should get a similar error message:
I have help you submit a feedback on Microsoft Connect Page, you can track the detailed information here: https://connect.microsoft.com/VisualStudio/feedback/details/2699963
Update:
According to the information in Microsoft Connect Page, there is no Hosted Build Controller for new VSTS account. So you need to setup your own on-premise build controller to fix the issue for Classic Portal.
I am trying to link the Azure Functions deployment to integrate with Visual Studio Team Service however once I select VSTS as the source, it doesn't show any other projects.
I have other web apps in my account which feed from a VSTS project.
The reason this is important to us is because of the workflow. We currently use AWS API Gateway + Lambda for our webhooks however it doesn't fit our development/deployment workflow.
When you select "Visual Studio Team Services" as deployment source from New Azure Portal, it is using Kudu service which is designed for Git version control. So it will only show the projects with "Git" repositories.
Kudu is the engine behind git deployments in Azure Web Sites. It can
also run outside of Azure.
If you want to deploy the TFVC project, try with Azure Classic Portal. You can refer to this article for details: Continuous delivery to Azure using Visual Studio Team Services