in my company we're using Azure DevOps hosted on-premises. We have an internal team managing Azure DevOps Server and we need to disable the auto-update function for some (or even all) Azure extensions as SonarQube, because some new versions cause our build pipelines (they are nearly a hundred) failure.
How it is possible to disable auto-update function, so we can schedulate updates to have minimum impacts.
We prefer, if there is a way, to disable auto-update of DevOps extensions using Azure DevOps Server managing console.
Thank for anyone help.
According to your description, currently there is no option to control the auto-update Azure DevOps Extensions.
You could use "Request a feature" on the left side of Azure DevOps Developer Community to open a new suggestion ticket.
Related
I have the following problem to solve but I cannot find the right documentation.
I just upgrade the version control software from TFS (on premise) to Azure Devops Service.
I have my own self-hosted building agents that are hooked upo with the TFS istance.
What I want to do now is to redirect them from pointing to TFS to pointing into Azure Devops Service.
I can find everything about the authentication part, token and so on but I miss the basic steps on reconfiguring the building agents themselves. Can someone help me by any chance?
You can reconfigure your build agents into Azure DevOps. Remove and re-configure an agent
To remove the agent:
.\config remove
After you've removed the agent, you can configure it again.
I am trying to understand the relationship between VSTS and AZURE.
I am planning to deploy some apps in Azure and wanted to know if there is any way within Azure that we can maintain releases and builds? or do we have to use VSTS?
EDIT
I currently have everything in on-premise TFS and am using on-premise MS Release Management for managing my releases (which are a bit complicated).
Now Azure does offer continuous deployment using App Service integration but I feel that might be more apt for simpler applications with relatively simple release plans (Is this assumption correct?). Exploring Azure, I also see Octopus deploy (in the compute section). Does that mean that we can manage deployment inside of Azure without using VSTS? (I currently dont care about work items, backlogs and process inside of TFS)
Regarding the relationship between VSTS and Azure.
Want to authenticate users and control access with Azure AD Team Services: Access with Azure Active Directory (Azure AD)
Set up billing when you need more users, pipelines etc… Set up billing to pay for users, pipelines, and cloud-based load testing in Visual Studio Team Services
Regarding deploy apps to azure, there are many ways, for example:
Continuous Deployment to Azure App Service, the source code could be in VSTS, Git, Bitbucket etc…
VSTS build and release, the source code can be in VSTS, GitHub, External Git and Subversion: Build definition repository
Some tools, for example Visual Studio: Using Visual Studio 2015 and Deploying your first web app to your FREE Azure Subscription
I'm trying to automatically deploy from Team Services (was Visual Studio Online) after a successful build a C# program to an azure app service without success.
I can only do it to a cloud service (classic) rather app service.
I've seen that I could plug Team Services directly to the app service with "deployment source" (I did tried so far because both tenant, Team Services & Azure one are different and requires some effort)
but wouldn't it break the normal release / test process from Team Services?
I can only find little information over internet regarding these topics ...
Any help would be appreciated.
You can also add a FTP Upload task in your build definition to publish the output to Azure App Service via FTP Method.
To publish to an Azure App Service, you need to use either of the following Agent tasks:
Here is a walkthrough: https://www.visualstudio.com/en-us/docs/build/apps/aspnet/aspnet4-to-azure
When making a new build definition, it is easiest to choose the Deployment -> Azure WebApp option.
How can I publish to an Azure Website (NO VM!) using Microsoft Release Management.
At the moment, ms release management only seems to support deploying to Azure VM's. I like MS Release Management system as it lets me control my deployment variables across multiple deployment stages.
Basically, this is not a supported scenario out of the box.
Your best bet here is to use an agent-based release template with a "springboard" server to manage the release, and custom PowerShell scripts that use the Azure SDK to interact with Azure. One of my colleagues did the leg work to figure it out a few months ago, and has a few comprehensive blog posts describing how he accomplished deploying an Azure Web Application via RM.
Visual Studio Release Management now offers built-in steps to manage Azure App Services. In a Release Management process add the Azure App Service Deploy step, and configure for your website. Note that this step requires your site to be published as a .zip file.
In addition to the deploy step, it is best practice to deploy to an inactive slot, or stop / start the site using the Azure App Service Manage steps in Release Management.
For now, you should take a look at the new build system, it has an out of box task to deploy a package to azure web app.
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...