Absolute path to a directory where builds will be stored in context of selected executor (Locally, Docker, SSH).

This optional key specifies whether the kernel should consider this daemon to be low priority when doing file system I/O.

This optional key specifies whether the job participates in advanced communication with launchd

This optional key specifies whether the job can only be run once and only once

Path of the source file.

This optional key specifies whether initgroups(3) should be called before running the job

This configuration file only applies to the hosts listed with this key

This configuration file only applies to hosts NOT listed with this key

This optional key specifies what file should be used for data being supplied to stdin when using stdio(3).

Path of the source file.

This optional key specifies whether the kernel should consider this daemon to be low priority when doing file system I/O.

Disables adding the default labels

This optional key specifies what file should be used for data being sent to stdout when using stdio(3).

This key maps to the first argument of execvp(3)

This optional key specifies whether the job can only be run once and only once

This optional key specifies what file should be used for data being supplied to stdin when using stdio(3).

Runner-specific command script executed before code is pulled.

This optional key specifies that launchd should instruct the kernel to have the job wait for a debugger to attach before any code in the job is executed.

Whether to allow read access to FHS paths like /etc and /var.

This configuration file only applies to hosts NOT listed with this key

Whether this file should be generated

This optional key specifies what file should be used for data being sent to stdout when using stdio(3).

The command hook script will replace the default implementation of running the build command.

Extra commands to run before starting buildkite.

This optional key specifies whether the kernel should consider this daemon to be low priority when doing file system I/O.

List of paths that should be read-only inside the sandbox.

Whether this file should be generated

This key specifies that the job should be spawned into a new security audit session rather than the default session for the context is belongs to

Runner-specific command script executed after code is pulled, just before build executes.

This optional key specifies that launchd should instruct the kernel to have the job wait for a debugger to attach before any code in the job is executed.

List of paths that should be read/write inside the sandbox.

The pre-command hook will run just before your build command runs

This optional key is used to specify a directory to chroot(2) to before running the job.

This optional key specifies what file should be used for data being supplied to stdin when using stdio(3).

Add a custom host-to-IP mapping.

This key specifies that the job should be spawned into a new security audit session rather than the default session for the context is belongs to

This optional key specifies what file should be used for data being sent to stderr when using stdio(3).

This flag causes launchd to use the glob(3) mechanism to update the program arguments before invocation.

This optional key specifies what file should be used for data being sent to stdout when using stdio(3).

The full path to a file which contains either

• a fine-grained personal access token (PAT),
• a classic PAT
• or a runner registration token

Changing this option or the tokenFile’s content triggers a new runner registration

Runner-specific command script executed after code is pulled and just after build executes.

This configuration file only applies to sessions of the type specified

This optional key is used to specify a directory to chroot(2) to before running the job.

Select executor, eg. shell, docker, etc

The maximum amount of cpu time (in seconds) to be used by each process.

The maximum amount of cpu time (in seconds) to be used by each process.

The post-command hook will run after the bootstrap script has run your build commands

This optional key specifies that launchd should instruct the kernel to have the job wait for a debugger to attach before any code in the job is executed.

Register to run untagged builds; defaults to true when tagList is empty.

This flag causes launchd to use the glob(3) mechanism to update the program arguments before invocation.

This optional key specifies what file should be used for data being sent to stderr when using stdio(3).

This configuration file only applies to sessions of the type specified

A list of verbatim OpenSSH public keys that should be added to the user's authorized keys

The largest size (in bytes) core file that may be created.

The largest size (in bytes) core file that may be created.

This key specifies that the job should be spawned into a new security audit session rather than the default session for the context is belongs to

Bind-mount a volume and create it if it doesn't exist prior to mounting.

A list of files each containing one OpenSSH public key that should be added to the user's authorized keys

The maximum amount of cpu time (in seconds) to be used by each process.

The maximum amount of cpu time (in seconds) to be used by each process.

This optional key is used to specify a directory to chroot(2) to before running the job.

OpenSSH private key

A run-time path to the key file, which is supposed to be provisioned outside of Nix store.

The pre-artifact hook will run just before artifacts are uploaded

Resource limits to be imposed on the job

Resource limits to be imposed on the job

This flag causes launchd to use the glob(3) mechanism to update the program arguments before invocation.

This optional key specifies what file should be used for data being sent to stderr when using stdio(3).

This configuration file only applies to sessions of the type specified

The largest size (in bytes) core file that may be created.

The largest size (in bytes) core file that may be created.

The post-artifact hook will run just after artifacts are uploaded

The maximum amount of cpu time (in seconds) to be used by each process.

The maximum amount of cpu time (in seconds) to be used by each process.

The largest size (in bytes) file that may be created.

The largest size (in bytes) file that may be created.

Resource limits to be imposed on the job

Resource limits to be imposed on the job

When set to true Runner will only run on pipelines triggered on protected branches.

The pre-checkout hook will run just before your projects source code is checked out from your SCM provider

Disable all container caching.

The checkout hook script will replace the default checkout routine of the bootstrap.sh script

The largest size (in bytes) core file that may be created.

The largest size (in bytes) core file that may be created.

The post-checkout hook will run after the bootstrap script has checked out your projects source code.

Modify the service

The largest size (in bytes) file that may be created.

The largest size (in bytes) file that may be created.

This optional key causes the job to be started every N seconds

When a job dies, launchd kills any remaining processes with the same process group ID as the job

The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call.

The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call.

Resource limits to be imposed on the job

Resource limits to be imposed on the job

This optional key causes the job to be started every N seconds

When a job dies, launchd kills any remaining processes with the same process group ID as the job

This optional key is used to specify a directory to chdir(2) to before running the job.

Regex substring to match the app name (optional).

The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call.

The maximum size (in bytes) of the data segment for a process; this defines how far a program may extend its break with the sbrk(2) system call.

The largest size (in bytes) file that may be created.