Skip to content

Instantly share code, notes, and snippets.

@nodirt
Last active February 22, 2018 23:39
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save nodirt/0592b57be00f2b3dcd20e4e73a427f51 to your computer and use it in GitHub Desktop.
Save nodirt/0592b57be00f2b3dcd20e4e73a427f51 to your computer and use it in GitHub Desktop.
// Time of the event creation.
TIMESTAMP create_time
// The state of the build at the completion time.
RECORD build {
INTEGER x
// Buildbucket build id.
INTEGER id
// ID of the project containing the bucket that contains this build.
STRING project
// The bucket containing the build.
STRING bucket
// The builder name of the bucket.
// In Buildbucket API v1, comes from the "builder_name" build parameter.
STRING builder
// Build number.
// NULL if build numbers are not enabled.
INTEGER number
// True if this build used canary version of the infrastructure.
BOOLEAN canary
// Time of the build creation.
TIMESTAMP create_time
// Time of the build start.
TIMESTAMP start_time
// Time of the build completion.
// Close to the time when this event was published.
//
// If this build is a part of BuildCompleted event, end_time must be set.
TIMESTAMP end_time
// The host name of the machine that ran the build.
STRING host_name
// Current state of the build.
//
// If this build is a part of BuildCompleted event, status is must be
// terminal, i.e. not SCHEDULED or STARTED.
// Valid values: SCHEDULED, STARTED, SUCCESS, FAILURE, ERROR, CANCELED, TIMEOUT.
STRING status
// Time of the most recent status change.
//
// If this build is a part of BuildCompleted event, status_update_time is
// the time of the last status change.
TIMESTAMP status_update_time
// Buildsets, see go/buildbucket-buildset for format.
// Identifies a patchset or commit.
repeated STRING buildsets
// Build tags, colon-separated key-value pairs.
// A single key may have multiple values.
// Values may contain colon(s).
repeated STRING tags
// Build input, defines what the build should do.
RECORD input {
// User-defined input properties, for example "revision"
// whch is a typical way to specify the revision to fetch.
STRING properties
}
// Build output, the product of the build.
RECORD output {
// Properties at the end of the build, generally include input properties,
// but also any properties added/modified by the recipe during execution.
//
// Historically, output properties include "got_revision" produced by
// bot_update step, but going forward Source Manifests should be used for
// this, see below.
STRING properties
}
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment