DevOps build-pipeline overview & sound trigger on fail - audio

I want to setup a monitor were my development team can see the current status of our build-pipelines. When a build-pipeline fails, I want to trigger a sound. I don’t know if it is even possible in Azure DevOps but that’s why I’m asking it here.
Also, if somebody has some good advice for configuring this monitoring ‘dashboard’, please let me know!
Kind regards,
Wouter

You can create your on own dashboard (Add, rename, and delete dashboards in Azure DevOps) with build-in pipeline widgets (Azure Pipelines widgets). Additionally, you can use extensions from the marketplace:
Team Project Health
Project Tile
CI/CD Dashboard
You can try CatLight for notifications on a local workplace.

Related

Change the git repo url and branch in Azure app service

In the absence of the person who normally does this, I've been asked to change the repo url and branch in the Azure app service in this image.
I can see what the values are currently but I can't find how to change them, can anyone point me in the right direction?
Thanks
We use Azure DevOps for CI/CD and we set all those values in the build and release on that end. They show in the Azure Portal but are read only reporting where it came from. May be the same case with how you are deploying.

Is it possible to add a CI/CD pipeline to an existing app service on Azure? If so, how?

I have an existing app service running on Azure that I previously published directly from Visual Studio. I am trying to get to grips with using DevOps and was wondering if it is possible to add a CI/CD pipeline to an existing app service.
I have seen a lot of tutorials on the web about how to create a pipeline for a new app service (many, of course, are out of date and do not actually relate to what one sees in the Azure portal!) So far, though, I have not come across anything about adding this to an existing app service.
Any advice or links to handy tutorials would be greatly appreciated!
I am hoping that the answer is not delete the existing service and start again from scratch!
If you are a beginner on Azure Devops, I will recommend to use the Azure Devops Starter project to create a pipeline, you can pick AppService as the deployment.
Once the pipelines are created on the Azure Devops , just open the pipeline and select the existing AppService where you want to deploy and also the source from where you want to pull the code. This makes easier rather than creating the stuffs from the scratch.

How to move Azure DevOps Project to another Organization with all the history?

I've got a project under my user that I want to move to my Azure DevOps Organization.
I can only see the option to move repository through Import functionality but not a Project.
I can't see any options in Azure DevOps on migrating projects.
Anyone know how to do it?
Thanks
This is not supported today. But this feature is up there on the pipeline as you can see.

On deploy trigger a webhook in Azure?

I have an Azure App Service set up to deploy from a local git branch. (per instruction from this article). I would like these deployments to trigger another webhook I have set up that posts deploy logs to slack, but I don't see any way to configure a push option in the Azure UI.
Any tips or ideas on how to accomplish this?
You can use Azure Functions to do that.
Here's an Official Azure Documentation article that will help you to work with HTTP triggers and output bindings in Azure Functions
If this solves your problem, do not forget to click on Mark as Answer

Azure VSO Continuous Delivery: Deploy specific site in multi-site solution

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...

Resources