Ignorar navegação

A equipe de infraestrutura do .NET investe em consistência para acelerar a inovação de software livre

Veja como as ferramentas compartilhadas e um único sistema de CI compartilhado nos repositórios do GitHub oferecem enormes ganhos na produtividade do desenvolvedor.

Leia a história completa

O desafio: Simplificar a colaboração para colaboradores de software livre

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, engenheiro de software principal, Serviços de Engenharia do .NET

Melhorar a produtividade por meio de ferramentas compartilhadas e um único sistema de 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, engenheiro de software principal, Serviços de Engenharia do .NET

Melhor colaboração gera um produto melhor

Agora os desenvolvedores podem facilmente mover de um repositório para outro, rastrear a causa raiz de um bug e propor e testar correções – tudo isso sem precisar ter o conhecimento especializado que era necessário no passado. Essa colaboração simplificada de software livre no GitHub permite que os desenvolvedores inovem de forma mais rápida conforme trabalham juntos para gravar, testar, criar e fornecer software de alta qualidade. Como a equipe de Serviços de Engenharia do .NET pode fazer alterações na infraestrutura em toda a pilha, ela oferece melhorias nas ferramentas que os desenvolvedores podem utilizar em todos os repositórios com muito mais rapidez e eficiência.

Veja uma análise mais detalhada do percurso e da tomada de decisão das equipes.

Leia a história completa