• Scaling Git (and some back story)

    Home » Forums » Developers, developers, developers » DevOps Lounge » Scaling Git (and some back story)

    Author
    Topic
    #91633

    Server & Tools Blogs > Developer Tools Blogs > Brian Harry’s blog

    Brian Harry’s blog
    Everything you want to know about Visual Studio ALM and Farming

    Brian Harry’s blog

    Scaling Git (and some back story)

    https://blogs.msdn.microsoft.com/bharry/2017/02/03/scaling-git-and-some-back-story/

    02/03/2017 by Brian Harry MS

    A couple of years ago, Microsoft made the decision to begin a multi-year investment in revitalizing our engineering system across the company. We are a big company with tons of teams – each with their own products, priorities, processes and tools. There are some “common” tools but also a lot of diversity – with VERY MANY internally developed one-off tools (by team I kind of mean division – thousands of engineers).

    There are a lot of downsides to this:

    Lots of redundant investments in teams building similar tooling
    Inability to fund any of the tooling to “critical mass”
    Difficulty for employees to move around the company due to different tools and process
    Difficulty in sharing code across organizations
    Friction for new hires getting started due to an overabundance of “MS-only” tools
    And more…
    We set out on an effort we call the “One Engineering System” or “1ES”. Just yesterday we had a 1ES day where thousands of engineers gathered to celebrate the progress we’ve made, to learn about the current state and to discuss the path forward. It was a surprisingly good event.

    --------------------------------------

    1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

    SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

    CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
    Graphics Radeon RX 580, RX 580 ONLY Over Clocked
    More perishable

    2xMonitors Asus DVI, Sony 55" UHD TV HDMI

    1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
    1xOS W8.1 Pro, NAS Dependent, Same Sony above.

    -----------------

    Viewing 0 reply threads
    Author
    Replies
    • #91664

      GITHub is/has become a massive Repository of software, so much so, that the Chinese have taken to attacking it. I am very much a novice when it come to this new, more centralize(Gen 2) form of Repository like GitHub, PS Gallery, Chocolatey that in some form ???run on GIT???.

      I find it fascinating because I keep running into GibHub Directions for Downloads and I don’t quite know what to do there. So this is a journey of learning, teaching and discussing this new way of distributing software compared to your Grandmother’s day where we downloaded from the Apps site, or the various Gen 1(many are not so HEALTH to click at, BE CAREFUL) download sites. 😆

      Welocome aboard!….

      --------------------------------------

      1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

      SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

      CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
      Graphics Radeon RX 580, RX 580 ONLY Over Clocked
      More perishable

      2xMonitors Asus DVI, Sony 55" UHD TV HDMI

      1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
      1xOS W8.1 Pro, NAS Dependent, Same Sony above.

      -----------------

    Viewing 0 reply threads
    Reply To: Scaling Git (and some back story)

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: