DevOps Openhack

DevOps Openhack Badge
  • Require multiple people to review a code change before it can be merged into master.
  • Assign a work item using Azure boards to a code change — all code changes need to have a reason, why it was done, who asked for it, who signed it off?
  • Creating Azure pipelines (a workflow) to automate the building, unit testing and packaging, only executing when a code change is made. Our team created 4 different pipelines, one for dot net, node.js, java and go applications.
  • Using the pipeline to create a bug in the backlog for each failed build.
  • Implement continuous deployment to deploy a container image to an Azure App service.
  • Implementing a blue / green deployment scenario — this involves two environments (production and staging) and shifting the routing between them to avoid any downtime. If there is an issue with the new version, rolling back simply requires reverting traffic routing to the previous deployment.
  • A/B testing for directing different amounts of users to the production or staging web app. This can be useful to test new features in the application, conversion rates etc.
  • Implement a monitoring strategy using Azure Monitor.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jack Roper

Jack Roper


A tech blog about Cloud and DevOps. Specializing in Azure, Azure DevOps, Terraform & Kubernetes! ☁️