Creating a new builder

This doc describes how to set up a new builder on LUCI. It's focused on chromium builders, but parts may be applicable to other projects.


For a typical chromium builder using the chromium recipe, you'll need to acquire hardware and then land three CLs:

  1. in infradata/config, modifying swarming's bots.cfg.
  2. in chromium/tools/build, modifying the chromium_tests configuration.
  3. in chromium/src, modifying all of the following:
    1. LUCI service configurations in //infra/config
    2. Compile configuration in //tools/mb
    3. Test configuration in //testing/buildbot

Obtain hardware

If you‘re setting up a new builder, you’ll typically need hardware to run it. For CI / waterfall builders or manually triggered try builders, file a labs bug (internal). For CQ try bots, please file a capacity bug (internal) first. In both cases, note that your builder will be running on swarming (not on buildbot) and should be provisioned accordingly.

Pick a name and a master

Your new builder's name should follow the chromium builder naming scheme.

We still use master names to group builders in a variety of places (even though buildbot itself is largely deprecated). FYI builders should use, while other builders should mostly use chromium.$OS.

Note: If you're creating a try builder, its name should match the name of the CI builder it mirrors.

Register hardware with swarming

Once you‘ve obtained hardware, you’ll need to associate it with your new builder in swarming. You can do so by modifying the relevant swarming instance's configuration.

Swarming‘s bots.cfg schema is here. chromium-swarm’s bots.cfg instance is here.

You'll want to add something like the following:

bot_group {
  dimensions: "builder:$BUILDER_NAME"
  # Add a brief comment about hardware, particularly if you're doing
  # anything unique or atypical.
  bot_id: "$HARDWARE"

  # is typically fine for generic chromium builders.
  # If you're doing something more specialized, or if you're creating
  # a non-chromium builder, consider a different list.
  owners: "$OWNER_EMAIL"

  # See the schema for more information on these options. The values
  # listed below should be reasonable defaults for chromium builders.
  auth {
    require_luci_machine_token: true
    ip_whitelist: "chromium-swarm-bots"

  # This is the service account used by the swarming bot to authenticate to
  # LUCI services for system purposes (i.e., not within tasks).
  # For chromium builders, the bots-chrome@ account below should be fine.
  system_service_account: ""

  # POOL_NAME should be:
  #   - for public chromium CI / waterfall builders
  #   - luci.chromium.try for public chromium try builders
  dimensions: "pool:$POOL_NAME"

Recipe configuration

Recipes tell your builder what to do. Many require some degree of per-builder configuration outside of the chromium repo, though the specifics vary. The recipe you use depends on what you want your builder to do.

For typical chromium compile and/or test builders, the chromium and chromium_trybot recipes should be sufficient.

To configure a chromium CI builder, you‘ll want to add a config block to the file in recipe_modules/chromium_tests corresponding to your new builder’s master name. The format is somewhat in flux and is not very consistent among the different masters, but something like this should suffice:

'your-new-builder': {
  'chromium_config': 'chromium',
  'gclient_config': 'chromium',
  'chromium_apply_config': ['mb', 'ninja_confirm_noop'],
  'chromium_config_kwargs': {
    'BUILD_CONFIG': 'Release', # or 'Debug', as appropriate
    'TARGET_BITS': 64, # or 32, for some mobile builders
  'testing': {
    'platform': '$PLATFORM', # one of 'mac', 'win', or 'linux'

  # Optional: where to upload test results. Valid values include:
  #   'public_server' for
  #   'staging_server' for
  #   'no_server' to disable upload
  'test_results_config': 'public_server',

  # There are a variety of other options; most of them are either
  # unnecessary in most cases or are deprecated. If you think one
  # may be applicable, please reach out or ask your reviewer.

For chromium try builders, you'll also want to set up mirroring. You can do so by adding your new try builder to

A typical entry will just reference the matching CI builder, e.g.:

TRYBOTS = freeze({
  # ...

  'tryserver.chromium.example': {
    'builders': {
      # If you want to build and test the same targets as one
      # CI builder, you can just do this:
      'your-new-builder': simple_bot({
        'mastername': 'chromium.example',
        'buildername': 'your-new-builder'

      # If you want to build the same targets as one CI builder
      # but not test anything, you can do this:
      'your-new-compile-builder': simple_bot({
        'mastername': 'chromium.example',
        'buildername': 'your-new-builder',
      }, analyze_mode='compile'),

      # If you want to build and test the same targets as a builder/tester
      # CI pair, you can do this:
      'your-new-tester': simple_bot({
        'mastername': 'chromium.example',
        'buildername': 'your-new-builder',
        'tester': 'your-new-tester',

      # If you want to mirror multiple try bots, please reach out.

  # ...

Chromium configuration

Lastly, you need to configure a variety of things in the chromium repo. It's generally ok to land all of them in a single CL.

LUCI services

LUCI services used by chromium are configured in //infra/config.


Buildbucket is responsible for taking a build scheduled by a user or an agent and translating it into a swarming task. Its configuration includes things like:

  • ACLs for scheduling and viewing builds
  • Swarming dimensions
  • Recipe name and properties

Buildbucket‘s configuration schema is here. Chromium’s buildbucket configuration is here.

A typical chromium builder won‘t need to configure much. Adding a builders entry to the appropriate bucket ( for CI / waterfall, luci.chromium.try for try) with the new builder’s name, the mixin containing the appropriate master name, and perhaps one or two dimensions should be sufficient, e.g.:

buckets {
  name: ""

  swarming {

    builders {
      name: "your-new-builder"

      # To determine what you should include here, look for an
      # existing mixin containing
      #   recipe {
      #     properties: "mastername:$MASTER_NAME"
      #   }
      mixins: "$MASTER_NAME_MIXIN"

      # Add other mixins and dimensions as necessary. You will
      # usually at least want an os dimension configured, so if
      # none of your included mixins have one, consider adding one.


Milo is responsible for displaying builders and build histories on a set of consoles. Its configuration includes the definitions of those consoles.

Milo‘s configuration schema is here. Chromium’s milo configuration is here.

A typical chromium builder should be added to one or two consoles at most: one corresponding to its master, and possibly the main console, e.g.

consoles {
  name: "$MASTER_NAME"
  builders {
    name: "buildbucket/$BUCKET_NAME/$BUILDER_NAME"

    # A builder's category is a pipe-delimited list of strings
    # that determines how a builder is grouped on a console page.

    # A builder's short name is a string up to three characters
    # long that lets someone uniquely identify it among builders
    # in the same category.
    short_name: "$ID"

Scheduler (CI / waterfall builders only)

The scheduler is responsible for triggering CI / waterfall builders.

Scheduler‘s configuration schema is here. Chromium’s scheduler configuration is here.

A typical chromium builder will need a job configuration. A chromium builder that's triggering on new commits or on a regular schedule (as opposed to being triggered by a parent builder) will also need a trigger entry.

trigger {
  id: "master-gitiles-trigger"


  # Adding your builder to the master-gitiles-trigger
  # will cause your builder to be triggered on new commits
  # to chromium's master branch.
  triggers: "your-new-ci-builder"

job {
  id: "your-new-ci-builder"

  # acl_sets should either be
  #  - "default" for builders that are triggered by the scheduler
  #     (i.e. anything triggering on new commits or on a cron)
  #  - "triggered-by-parent-builders" for builders that are
  #    triggered by other builders
  acl_sets: "default"

  buildbucket: {
    server: ""
    bucket: ""
    builder: "your-new-ci-builder"

Recipe-specific configurations

chromium & chromium_trybot

The build and test configurations used by the main chromium and chromium_trybot recipes are stored src-side:

  • Build configuration: the gn configuration used by chromium recipe builders is handled by MB. MB's configuration is documented here. You only need to modify it if your new builder will be compiling.

  • Test configuration: the test configuration used by chromium recipe builders is in a group of .pyl and derived .json files in //testing/buildbot. The format is described here.

Questions? Feedback?

If you‘re in need of further assistance, if you’re not sure about one or more steps, or if you found this documentation lacking, please reach out to or file a bug!