Skip to content

DevOps

  • in DevOps
  • 2 min read

Azure & Terraform: The Tiny but Important Difference Between Windows & Linux

As part of the release build of our user group site, we use Terraform to create a BDD environment from scratch, run the acceptance tests and then destroy the environment to keep the cost down. As we recently switched the BDD environment from Windows to Linux, we run into this error:

Error: creating Linux Web App: (Site Name "***" / Resource Group "***"): web.AppsClient#CreateOrUpdate: Failure sending request: StatusCode=409 -- Original Error: Code="Conflict" Message="There was a conflict. AlwaysOn cannot be set for this site as the plan does not allow it. For more information on pricing and features, please see: https://aka.ms/appservicepricingdetails "

  • in DevOps
  • 1 min read

How to Grant Permissions to Create Sprints in Azure DevOps

Before you can assign work items to a sprint (or an iteration) in Azure DevOps, someone needs to create those sprints. That boring task is a great candidate for delegation. Unfortunately, the only role that can do this work by default is the project administrator. Before you turn everyone into a project administrator, let me show you a much more granular way to achieve the same goal.

  • in DevOps
  • 2 min read

How to Find Out Who Restarted Your Windows Server

A few weeks ago, one of our Windows Server made a reboot in the middle of the day. That was not planned, so we wanted to know what happened. Windows logs events like the reboot in the event log. The challenge is to find the right message in the huge pile of unrelated log messages. As it turns out, we can use a filter and get the right message in no time.

Shorten Your Feedback Cycle

One of the most important ideas of agile software development is for me the short feedback cycle. Instead of working for weeks or even months at a problem on our own, we try to get feedback as fast as we can. That not only works with user stories; we can apply this idea to every task independently of its size.

I experienced a great example of this principle a few weeks ago. Using this example, I would like to give you an idea of how to put a principle into action. For the sake of brevity, I am using the format of a PAR statement (problem, action, result).

  • in DevOps
  • 2 min read

What to Do if Azure DevOps Builds Don't Run in New Agent Pool

We created a new build agent pool for Visual Studio 2022 in Azure DevOps. To check if everything works, we temporarily switched jobs to the new agent pool. That worked for most jobs, but not for all. A few where stubborn and keep running on the old agent pool. How can that be?

As it turns out there are three and not just two places where we can choose the agent pool.