Passer la navigation

L’équipe d’infrastructure .NET investit dans la cohérence pour accélérer l’innovation open source

Observez comment des outils partagés et un système CI unique et partagé dans les dépôts GitHub génèrent de gros gains de productivité pour les développeurs.

En savoir plus

Le défi : Rationaliser la collaboration pour les contributeurs open source

As an independent organization created to foster innovation through open development and collaboration, the .NET Foundation supports a large and complex set of open-source projects, including .NET Core. The Microsoft .NET Engineering Services team contributes to the project and is responsible for much of the infrastructure that enables contributors from around the world to work together.

With dozens of different git repositories on GitHub, a broad range of tools, and several different continuous integration (CI) systems in use across the project, there was a lot of confusion that inhibited productivity. The sheer scale of the project added to the complexity. For example, the Roslyn (C# compiler) repo alone runs more than 600,000 automated tests for one iteration of a pull request. With more than 50 pull requests per week, each with multiple iterations, the number of CI tests is in the billions. For CoreFx (libraries), the numbers are even higher. As the .NET Engineering Services team planned for the .NET Core 3.0 release, they decided to make big changes to establish greater consistency and enable contributors to realize the full potential of the project.

"A distributed repo structure and tooling makes it a lot harder for developers to move from one repo to another … And if it's this hard on Microsoft developers, how can we expect most individual contributors to figure it out?"

Matt Mitchell, Principal ingénieur logiciel, .NET Engineering Services

Amélioration de la productivité grâce à des outils partagés et à un seul système CI

To make it easier for developers to move between different parts of the software stack, the .NET Engineering Services team worked to bring all repos under a common directory structure, set of commands, and build-and-test logic. The team eliminated further barriers to productivity by moving all existing workflows from the different CI systems into a single system in Azure Pipelines. Because the system is fully managed, they no longer have the burden of managing the CI server infrastructure. The team is now practicing configuration as code through YAML files that are stored in GitHub, and YAML pipelines are used everywhere. Whereas some repos had previously done CI serially—requiring developers to sometimes wait two or three hours between iterations on their code—all CI pipelines are now parallelized to enable faster iterations.

"Now that we longer need to worry about the operational aspects of CI, we're free to focus on further improvements that will be felt by all—including Microsoft developers and individual contributors alike."

Matt Mitchell, Principal ingénieur logiciel, .NET Engineering Services

Une meilleure collaboration pour un meilleur produit

Aujourd’hui, les développeurs peuvent plus facilement passer d’un dépôt à l’autre, rechercher la cause première d’un bogue, et proposer et tester un correctif, le tout sans presque disposer des connaissances spécialisées dont ils avaient besoin par le passé. Cette collaboration open source rationalisée dans GitHub permet aux développeurs d’innover plus rapidement en travaillant ensemble pour écrire, tester, créer et livrer des logiciels de haute qualité. De plus, étant donné que l’équipe de services techniques .NET peut effectuer des modifications d’infrastructure sur l’ensemble de la pile, elle est en mesure d’apporter des améliorations d’outils dont les développeurs peuvent tirer parti beaucoup plus rapidement et efficacement dans tous les dépôts.

Examinez de plus près le parcours et le processus de prise de décision des équipes.

En savoir plus