Bazel uses Buildkite for continuous integration. The buildkite folder contains all the scripts and configuration files necessary to setup Bazel's CI on Buildkite.
Buildkite currently does not support anonymous viewing of build results (it‘s in the works) and for now requires one to be logged in before being able to trigger builds, view build and test results. We have set up a separate mechanism to view build and test results for pull requests and so as a contributor to Bazel you typically don’t need access to Buildkite. However, if you are a maintainer of a repository under the @bazelbuild organisation or a Bazel team member with sheriff duties you probably do need access, and if so please ping either @buchgr, @philwo or @fweikert and we will get you on Buildkite.
When you first log into Buildkite you are presented with a list of pipelines. A pipeline consists of steps that are executed either in sequence or in parallel and that all need to succeed in order for the pipeline to succeed. The Bazel organisation has dozens of pipelines. Here are a selected few:
HEAD
every four hours.