Infrastructure (‘infra’) refers to all of the servers and tools which the Chromium project depends on for development.
Most of these are maintained at Google by a dedicated team, but (almost) all of these are modifiable by anyone in the Chromium project.
To check out (most) of the Chromium Infra code use:
fetch infra
Note: you probably should NOT try and work on infrastructure code from a Windows box. This is somewhat based on lore, but generally infrastructure scripts aren't developed on Windows and tend to break there. For example, ‘fetch infra’ currently fails on Windows.
Join infra-dev@chromium.org for discussion of Chromium infrastructure related issues.
Most of our documentation is auto-generated from files in the infra respositories. You can see it here:
Services
** Service**** Source**** Repository** gclient, git cl, etc. depot_tools Chromiumcodereview.appspot.com Rietveld (chromium branch) code.google.comchromium.googlesource.com Gitiles code.google.comcrrev.com infra/appengine/cr_rev Infra chromium-status, blink-status, etc. infra/appengine/chromium_status Infra buildbot masters (build.chromium.org/p/*) build/masters Infra test-results.appspot.com blink/Tools/TestResultsServer Blink sheriff-o-matic.appspot.com blink/Tools/GardeningServer (frontend) infra/tools/builder_alerts/ (backend) Blink Infra gatekeeper (thing that closes the tree), recipes (modern builder configuration language), swarming (next-gen parallel testing) build/scripts/slave Infra chrome-infra-stats.appspot.com (stats on builds) infra/appengine/chrome_infra_stats Infra
Google employees can find more information at the internal Chrome Infrastructure site.