Sunday, April 28, 2019

MS Flow Options for Azure DevOps

Microsoft Flow is in the Microsoft's business application platform to work on IFTT basis. It has many connectors and Azure DevOps triggers have been added recently along with some of them being on preview.

Firstly, lets look at the triggers.

As it can be seen, the build completion, work item actions (creation, update, assigning and closing) as well as code actions are included for checkins. One question that may raise is why use Flow over inbuilt options on Azure DevOps when build happens? Both has their good and bad. With Flow, you get the ability to connect to many other platforms. Name it a OneDrive document, Tweet, email or any what you like. 

Saturday, April 27, 2019

Azure DevOps Data in PowerBI

Recently I was able to tryout the Azure DevOps connector for PowerBI and visualize some crazy charts to see the work in progress for one of the organizations. It is still at Beta stage but looks solid with the way how it behaves.

You can simply search and find it on the connector search when you go to Get Data button and click on the More option down.


Saturday, March 16, 2019

Azure Service Health Dashboard

Azure Service Health provides information on the Azure Service issues, health alerts and scheduled maintenance.

This is different and more user friendly than the Global Azure Status page which can be accessed from here

Wednesday, February 20, 2019

New 'Basic' Process for Azure DevOps

By default Azure DevOps supported Agile, Scrum and CMMI. If you know atleast one of these, that works a lot better for your task management with sprints. What would happen if you are a newbie? If you do not know any of these?

Luckily, Azure DevOps Team has thought about them too. Now it allows you to select 'Basic' as the work item process type.



Thursday, January 10, 2019

AKS Cluster Autoscaler is now on Preview

Cluster autoscaler (CA) is designed to manage the resource demand when the resource demand increases. CA does a good job on scaling up and down the cluster when in need.

  • CA will periodically check the pending pods or empty nodes for increasing the size of the AKS cluster. If possible, it will increase. 
  • This happens so fast, it will keep scanning the pending pods for every 10 seconds. 
  • It will remove the node if it is not needed for more than 10 minutes. 
  • Horizontal Pod Autoscaler (HPA) will update pod replicas and resources when needed. (Need to use HPA with CA)
  • If not enough or excess, CA will respond and act on it.