At the JFrog SwampUp conference in Napa earlier this year, Melody Meckfessel and former Google vice president Sam Ramji (now with Autodesk) were showing off the way Google makes its sausage. Unlike other less well curated development experiences, Google's process is worth examining and shouldn't leave anyone offended or covered in sausage leavings. For starters, Google's internal development processes and practices are immense. The numbers revealed by Meckfessel at the conference showed that over 500 million tests are run per day inside Google's systems. That's to accommodate over 4 million builds, daily. Why so many builds? Because Google's Bazel build system allows for near instant build processes, ensuring developers can quickly gain the feedback they need from their code.
At the JFrog SwampUp conference in Napa earlier this year, Melody Meckfessel and former Google vice president Sam Ramji (now with Autodesk) were showing off the way Google makes its sausage. Unlike other less well curated development experiences, Google's process is worth examining and shouldn't leave anyone offended or covered in sausage leavings.
For starters, Google's internal development processes and practices are immense. The numbers revealed by Meckfessel at the conference showed that over 500 million tests are run per day inside Google's systems. That's to accommodate over 4 million builds, daily.
Why so many builds? Because Google's Bazel build system allows for near instant build processes, ensuring developers can quickly gain the feedback they need from their code.