package infra.postsubmit

Get desktop application:
View/edit binary Protocol Buffers messages

• string name = 1

  Name of this build. Needs to be unique among all builds, and should match the regex `[a-z][a-z_]+`.

• string repository = 2

  Repository that this postsubmit builds code from. Should be one of: * `enfabrica/enkit` * `enfabrica/internal`

• oneof trigger

  • string cron = 3

    Interval on which to run the build. This is a normal cron schedule expression (https://crontab.guru/), except that the minutes fields can (and should) be a `?` rather than fixed; this will be translated into a stable value based on the name of this build, which allows builds to not all hammer infrastructure by starting e.g. every hour on the hour.

  • bool disabled = 11

    If set, the build is created but never run.

• repeated string include_patterns = 4

  Bazel target patterns to include in the build.

• repeated string exclude_patterns = 5

  Bazel targets to exclude from the build; should be a subset of include_patterns.

• repeated string include_tags = 9

  Tags to include in the build. If specified, targets will only be built if they contain at least one of the specified tags. exclude_tags (below) takes precedence: targets with tags that match any of exclude_tags (if specified) will still not be built, even if they are included via this mechanism.

• repeated string exclude_tags = 6

  Tags to exclude from the build; build will not build targets that: * are tagged with at least one of the specified tags * depend on a target tagged with at least one of the specified tags The build will also not run tests tagged with at least one of the specified tags.

• repeated string notification_emails = 7

  List of emails to get notifications when the build fails. Ideally this is a Google group email (create a group for the relevant dev team, if it does not exist) to record failures as well as any follow-up more publicly.

• string timeout = 8

  Timeout in seconds, terminated by `s`. Example: "60s" If possible, this timeout will be applied to the build + test portion of the build (as opposed to any warmup steps that need to take place); if this is not possible, it will be applied to the entire build.

• repeated string bazel_args = 10

  List of bazel arguments that are passed directly to the `bazel test` commandline. This field serves as an escape hatch for custom bazel behavior not covered by the above fields; popular bazel options may be replaced by an applicable field in the future.

• string rbe_instance = 12

  RBE instance to use to run build. Defaults to the currently-supported buildbarn instance, but can be changed in order to target a non-prod instance.

• string container_image = 13

  Docker image in which each step is performed. If not set, a default auto-updated version is used. This allows for testing specific images in some builds before deploying them more widely.

• repeated DebugStep debug_steps = 14

  Optional steps/checkers that can be added for debugging postsubmit issues.

• uint32 local_storage_size_gb = 15

  Size of local scratch storage needed while the postsubmit is running. Generally speaking, builds shouldn't need local storage, as the bulk of the computation is happening remotely. However, some builds download large artifacts unavoidably, so this exists as a workaround for this specific use-case. If set to zero or not set, a default value will be chosen that is suitable for the common use case.

Used in: Build

• oneof step

  • LargeFilePrinter large_file_printer = 1

    Print the top N largest files under a particular subtree. Useful for debugging issues where the runner disk is filling up.

Used in: DebugStep

• string base_dir = 1

  Dir under which to print large files. Files will be either in this dir directly, or one of its children.

• int32 top_n = 2

  Number of large files to print sizes for.