I have read that Microsoft announce Build Service and hosted build controller as shown in image below. I have have setup TFS preview using this article.
But When I am trying to connect my cloud service it says there no hosted control found.
Can you please tell me how to setup hosted build controller.
Announcing a Build Service for Team Foundation Service
Hosted Build Controller should be available by default. You shouldn't have to do anything to "set it up".
Here's what I see in my TFS Preview account.
Although TFS Preview has been having some issues lately. On Friday, builds that were queued, were stuck in the queued status for a long time before it got picked up for compilation & deployment.
Check the status here - http://tfspreview.com/en-us/support/current-service-status/
Related
For about 2 weeks now I am unable to web deploy from Visual Studio 2019 16.9.6. I have an ASP.NET Core 3.1 MVC application that I am trying to web deploy to a Linux App Service on Azure. When I try to publish I get the following errors:
Publish has encountered an error.
Build failed. Check the Output window for more details.
A diagnostic log has been written to the following location:
"C:\Users\ken\AppData\Local\Temp\tmpF3BF.tmp"
An error occurred when the request was processed on the remote computer.
The server experienced an issue processing the request. Contact the server administrator for more information.
Prior to two weeks ago I had no issues. The following is a list of items I have tried:
Stopped and started the app service
Stopped the app service and tried deploying while it was stopped
Reset the publish profile and re-imported it into Visual Studio
If I edit the publish profile and click "Validate Connection" it fails and gives the same error message as above:
An error occurred when the request was processed on the remote computer.
The server experienced an issue processing the request. Contact the server administrator for more information.
I am able to publish locally and use an FTPS client to connect to the app service and manually deploy the files.
I deleted the current publish profile and instead of downloading it from the Azure portal I used the new publish profile wizard built into Visual to create the publish profile. Once I did that everything started to deploy with no issues. I looked at what the difference is and it seems the publish profile I downloaded from Azure was missing an XML element called "IsLinux".
We have a App Service Enviroment https://learn.microsoft.com/en-us/azure/app-service/environment/intro I have set up an App in but I am struggling to either publish from my machine (I've added the URLs to my HOSTS file and I can see it in a browser) and cant see a clear way to publish it from Azure Dev Ops (my preferred option).
I'd be happy to be pointed to TFM but everything I find is out of date / not near the options I can see in Dev Ios or Visual Studio (2019 / 2019 Preview).
EDIT: Also note this is a multi project solution (various console apps, an API and a website it is the API / Website I want to publish)
EDIT 2: So "its always DNS" it was a DNS issue in trying to publish from Visual Studio
You can check these two links:
https://learn.microsoft.com/en-us/visualstudio/deployment/quickstart-deploy-to-azure?view=vs-2019
https://learn.microsoft.com/en-us/azure/app-service/deploy-continuous-deployment?tabs=github
If you use Visual Studio, see: Deploy an ASP.NET Web App in Azure App Service.
If you use Azure pipeline, this doc: Deploy an Azure Web App provides a tutorial to build web app and then deploy to an Azure Web App. Also see this video for detailed guidance: Build and deploy to an Azure Web App using VSTS (Quick Starts).
BTW, there are a few useful tools: Azure DevOps Labs, Azure DevOps Services Demo Generator, and DevOps Starter which will help you to get started with Azure DevOps services to automate software delivery and meet business needs.
I am trying to deploy a simple "Hello World!" .NET Core MVC 3.1 web application to an Azure App Service using the Azure Portal Deployment Center.
I created a my application using .Net Core version 3.1. (Visual Studio 2019 only has version 3.1 in the drop down, not 3.0.)
Visual Studio 2019 create wizard dropdown:
However this is not yet supported in the Deployment Center. You can select a runtime stack 3.1 (LTS) when adding creating the App Service Plan, but when you try and create a CI/CD pipeline with the Deployment Centre, it gives an error: "source.buildConfiguration.version: Property 'source.buildConfiguration.version' has invalid/unsupported value 'LTS'"
If I downgrade my web application to a version 3.0, and create the App Service/deployment pipeline with 3.0 using the Azure Portal Deployment Centre (building from my Azure Repo), it says the deployment has been successful, but it still shows the default site, not my "Hello World!" site.
Azure Devops Services indicates that the deployment has been successful:
Therefore, I expect to see my "Hello World!" site:
However, it still shows default site:
Given that there are no error messages, I'm not sure how best to debug what has gone wrong with the deployment. Any advice would be appreciated.
I ran into the same issue today... The solution was to change the
Startup Command (dotnet "myApp.dll" instead of dotnet run "myApp.dll")
under Configuration - General Settings in the App Service.
You might also check the Log Stream in your App Service for additional errors.
I also had to adjust the CD pipline task "Deploy Azure App Service" in Azure Devops to the Same Startup command.
Change .NET version to v4.8. Azure by default set it to v3.5, even though I selected 4.8 in the AppService wizard. My website uses v4.6.1.
And also, you have to change the document order in the configuration settings - default documents, in order to work and show the project enter image description here
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.
Im new to Azure and wanted to create a Continuous Integration build using TFS. I created a build definition but building my Cloud App with simple website using a hosted buildserver in the build definition fails with error:
C:\a\src\myAzure\myAzure\myAzure.ccproj (70): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.0\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I can however build locally, and manually Publish to Azure and it will deploy fine.
Im suspecting that the hosted buildserver of TFS does not support Azure 2.0?
Is there a way around this problem or will I have to forget the idea of using CI?
Seems to be so since the Build is a preview feature of the Team Foundation Service. There was the same thing with Azure SDK 1.8, but they updated the Build Servers in a couple of days. Hope that it will not take long this time.
UPDATE:
"No, TF Service hosted build machines do not have the new SDK 2.0 at this time. We expect all users to have Azure SDK 2.0 support post June 1st. In the meantime you will need to use an on-prem build controller with the bits you need and deploy to Azure from there."
(C) Trevor Hancock from Microsoft
http://social.msdn.microsoft.com/Forums/en-US/azuretfs/thread/2df796d5-1abb-4b89-a571-0b7a62b80d55
UPDATE 2:
I've managed to complete a successful build using TFS build servers with SDK 2.0 So I think this problem is resolved for now. In future I recommend not to do updates to new versions of Azure SDK until the TFS build servers are ready.