Using VSO Team Project and Azure Web App.
I want to connect these services together, however, when I set up Continuous deployment it always fires this error:
My subscription is free DreamSpark.
What can I do?
Setting up CI with VSO TFS is not supported for Dream spark subs. It looks like we have a bug in the UI if you are getting this far.
Related
I have a release pipeline to deploy my ASP.NET MVC web app to Azure VM. I have configured the release pipeline and everything was working fine.
But all of a sudden, it started throwing the error shown here. I am using IIS Web App deployment tool for this in Azure DevOps:
Looks like it's been reported as an issue related to a new task versions for WebAppDeployment tasks. See here, you might find a workaround that will work for you: https://github.com/microsoft/azure-pipelines-tasks/issues/17634
I have release azure function app from VSO Azure App Service Deploy release task,
it gives:
System.Nets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions I searched on google, people say the sockets get expired but i am using S3 pricing tier
I have then released the same function app from Visual Studio 2017 which runs perfectly fine without any exceptions.
I am attaching the artifacts, build assets, release pipeline details, please help. I will not be able to move to production unless this issue is resolved.
Structure of Artifacts which is not working
Structure of artifacts which is working fine-published from VS2017
Here is the github link for more details regarding the issue.
https://github.com/microsoft/azure-pipelines-tasks/issues/11345
I had to give a proper storage connection string for the following, instead of UseDevelopmentStorage=true,
Sorry, less a code issue but a process issue in deploying through Microsoft VSTS. I'm deploying an ARM template via a VSTS build definition and it failed (complaining the storage account was not in the same RG as the VM ).. BUT in the azure portal against the RG it shows a successful deployment and the resources deployed as expected.
What would cause VSTS to report an issue this way? Obvious issue is my deployment technically fails as a VSTS job despite being fine in Azure.
with no changes is stopped erroring so i'm guessing something on the azure side. Thanks anyway
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
We have a VSO repository with multiple sites in the same solution. We want to be able to deploy our sites independently of each other to Azure with continuous delivery. Right now the first site alphabetically is deployed to all our sites which of course is not desirable.
Is this possible to achieve?
I have tried to set the Project key to the correct csproj in App Settings like suggested here: https://github.com/projectkudu/kudu/wiki/Customizing-deployments without any success. Maybe Kudu is not used for VSO?
Any help would be greatly appreciated!
You should move away from trying to do this in a build, especially if you want that level of control.
You have Release Management Online provided with your VSO account and can use the Release Management client to configure your releases.
I believe that you can right-click on your Build and have an appropriate starter release template created when configured.
http://nakedalm.com/create-release-management-pipeline-professional-developers/
Here is an example of and end to end deployment with a web app. Deploying to Azure with RM is Childs play...