DevOps

ToolUp Tuesday is all about showing the thought process and decisions made when creating an application. Join Chris and Matt as they build a new application from the ground up, including development processes, tooling, service choices and architectural decisions!

I’ve been following the GitHub Projects beta for a while now, and have been fortunate to be accepted as an early adopter. I’m a big fan of the direction, and the flexibility. One of the limitations I’ve noticed is that there’s currently no built-in way to automatically add an issue to a project board. It’s on the backlog, but not yet available. Fortunately, GitHub Actions has us sorted. I’ll walk you through a sample I put together to do exactly that.

Did you know that Static Sites can help you build performant sites that easily scale globally? Better yet, they can be incredibly cost-effective!

A little while ago, I wrote a blog post on Using the GitHub self-hosted runner and Azure Virtual Machines to login with a System Assigned Managed Identity, which seems to get a good amount of views week on week. Reflecting on some questions that have popped up this week (and regularly received over my time in the DevOps space), I thought that it makes sense to write a post on how to use Azure DevOps self-hosted agents to deploy to private resources. So, that’s what we’ll be covering in this post!

Perf Testing has traditionally been a higher environment activity. This leads to issues such as performance issues being identified late in the cycle, high MTTR for such issues, unplanned work, etc. However applying ‘Shift Left’ to Performance Testing is a hard problem to solve. In this episode, Chris is joined by HariKrishnan as they talk through Hari’s experience in the hurdles encountered running perf tests on local machines / lower environments.

Ten years and more passed since Patrick Debois coined the term DevOps, in 2009. In the IT world, nothing is definitive. All the technologies and techniques continue to evolve following an innovation trend that we cannot stop. We cannot merely say: ‘I’m tired of changing; please give me a rest.’ The only option is to be ready for the change. In DevOps, there is a significant change because of the rise of the cloud and the market, always more demanding. The DevOps philosophy was adopted by most companies and bring essential improvements to quality and cost-saving. Anyway, the DevOps scenario is continuously evolving and adapting to the new market requirements. In this speech, we will analyze the new frontiers of DevOps and what to know to keep up with the times. Let’s see in this article what are the latest trends to follow.

Listen in to this session as Chris is joined by Thomas Thornton, as they talk about DevOps in real-world scenarios.

This post is similar to another I recently wrote on using Branch Protection Rules in GitHub. Instead of focusing on GitHub, we’ll be looking at how you can use Branch Policies in Azure DevOps (specifically, Azure Repos). If you’re using Azure Repos, but not using Branch Policies - I’d encourage you to start using them! I hope this post helps you learn how!

If you’re using GitHub as your source control provider, then I’d encourage you to using Branch Protection Rules if you’re not already doing so! In this blog post, we’ll cover what Branch Protection Rules are and how they can increase your code quality.

Chris is a Cloud Solution Architect at Microsoft. He’ll provide an overview of GitHub and explore how GitHub Actions can be used to build and deploy your own static sites (or other apps!) to Azure.