Using Azure DevOps REST API to start multiple releases with Azure Logic Apps

In our last article, we looked at how we could leverage the Azure DevOps REST API to trigger multiple releases.

This is useful when rebuilding an environment: first we release the shared infrastructure then each service on top of it.

In this article, we’ll see an implementation example using Azure Logic...

Using Azure DevOps REST API to start multiple releases

Azure DevOps CI / CD (i.e. Build / Release) mechanism is very valuable to me. It makes things reproduceable & robust. It allows me to change whatever I want since I have this constant safety net underneath.

For simple projects, having a build and release is fine. With micro-services I adopt the pattern of...

Understanding multiple Ingress in AKS

Last time, I covered the ins and outs of Ingress on AKS.

We looked at how to install nginx ingress controller and how the controller is deployed as a load balanced service. We did some URL based routing and domain name overloading.

This was in the spirit of clarifying the magic...

Understanding simple HTTP Ingress in AKS

We looked at Kubernetes Ingress conceptually. We looked at different use cases: URL based routing and multiple domains.

We also looked at how ingress was implemented from an AKS perspective, i.e. where traffic was routed in nodes.

In this article, I wanted to get hands on. I figured we could start...

Azure DevOps - Task output to a variable

I’ve been building a couple of Continuous Integration / Continuous Delivery (CI / CD) pipelines on Azure DevOps lately.

Azure DevOps is formerly known as Visual Studio Team Service (VSTS). As I mentioned recently, VSTS had nothing to do with Visual Studio and we’re very happy with the new brand name.

With...