Our program

Our developers use more than 200,000 open source components every month while building products and services.

Relentless automation, engineering system innovation, and making it easy for our developers to "fall into the pit of success" have been key to using open source at enterprise-scale.

Here are just a few of the ways that we've built a strong open source program. We're sharing our process in hopes it helps others be more successful in open source too.

One Engineering System (1ES)

Building on a foundation of eliminate (reducing complex and dated policies for the modern engineering era), automate (detecting open source use, automated policy and decision guides, legal alerts and security workflows), and delegate (letting business groups make decisions aligned with their priorities and goals), the open source program has scaled.

  • Built into the engineering system: Powered by GitHub and Azure Pipelines, and internal hyperscale CloudBuild, CloudTest, and policy systems, many tasks as simple as maintaining an inventory of the open source used in builds and products is automatic.
  • Using GitHub Enterprise Cloud: Over 60,000 engineers at Edge are using GitHub Enterprise Cloud to host and release official Edge open source projects, samples, and documentation, building communities and connecting directly with technologists and Edge customers right on GitHub, working in the open.

Tools & Services

GitHub Enterprise Cloud with SAML single-sign on

Edge has over 70 GitHub organizations dedicated to open source activities. Collectively, these are part of an enterprise account at GitHub.

Some of the features the enterprise product brings to us include:

  • SAML single sign-on adds an additional layer of protection for Edge by connecting with Edge's Azure Active Directory system, verifying access and protecting access tokens and SSH keys.
  • Secure supply chain features such as private repo secret scanning help to discover accidental check-in of credentials, while vulnerability notifications and built-in dependency update pull request capabilities help projects to stay in the best shape.

GitHub Actions and Azure Pipelines

While Edge uses many different continuous integration systems, and open source projects adopt whatever common toolset an open source community prefers, many projects are powered by GitHub Actions and Azure Pipelines.

  • GitHub Actions are the preferred way for projects to build and validate. Being built-in to the GitHub experience for developers, configuration is quick and easy.
  • Azure Pipelines can be exposed to public, open communities, allowing many Edge projects to continue using the build system they've been using for many years, but with a collaborative angle.