Skip to content

DevOps Enablement

The DevOps Enablement team (Energizers) seeks to enable DevOps culture through the facilitated sharing of DevOps best practices, examples, and templates so that teams can learn and grow their DevOps capabilities from each other.

Most of the items on this page are planned or aspirational over the coming years.

We seek to:

  • Simplify and standardize our tooling (e.g. migrate everybody to one AZDO org)
  • Maintain a wiki of DevOps best practices that allow us to simplify and standardize our work
  • Facilitate the capture and sharing of best practices across teams/projects
  • Capture great examples and code samples that demonstrate key concepts
  • Maintain code templates, such as pipeline templates that offer great reuse potential across teams/products
  • Host "office hours" and a cadence of DevOps lunch and learns
  • Curate training materials (e.g. Pluralsight courses)
  • Team coaching and consulting around DevOps practices

Planned Templates, Examples, and Walkthroughs:

Our plan is to capture great examples of DevOps practices amongst the various product teams and to help disseminate examples common to most software teams, such as best practices and examples for:

  • Git demonstration, step-by-step
  • Sample pipelines for:
    • Deploying a microservice to Kubernetes
    • Setup pipelines that interface with hardware/devices
    • Set up vanilla test pipeline for a service, app, web app, and exe
    • Set up vanilla CI/CD pipeline for a service, app, web app, and exe
  • Implementing a microservice
  • Adding SSL to a microservice
  • Enabling data encryption in your app
  • Istio for Kubernetes routing and intra-service communication policies
  • Configuring microservice ingress/egress
  • Managing secrets
  • DevOps/ALM/APM Data connectors to fast-track team's ability to connect to data for dashboarding purposes

TODO: POC what teams are doing to scope/discover examples/tutorials for how to advance their DevOps practices

Automating the Mundane

We also seek to develop automation for key business processes that require tons of manual human effort and are of little business value in and of themselves, such as:

Planned Automations:

  • Repo creation with all the default branch policies to enforce git-flow, standard git ignores, etc
  • SOUP release reporting
  • Test results release reporting
  • CI Merge approvals workflows
  • Posting/dashboard Azure/AWS/DevOps services that are down or experiencing a degradation of service availability
  • Automate cost reporting to cost center owners for their cloud/DevOps costs
  • Sonar user group adoption/coverage so that stakeholders can measure adoption