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

Extra labels in addition to the default (unless disabled through the noDefaultLabels option)

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

Whether to enable this buildkite agent

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

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.

Substring to match in the window title (optional).

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

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

Whether to match during aerospace startup (optional).

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.

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

Text of the file.

Default orientation for the root container.

Runner-specific command script executed before code is pulled.

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

List of Node.js runtimes the runner should support.

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

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

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.

Whether this file should be generated

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 configuration file only applies to sessions of the type specified

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).

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

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

Path of the source file.

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

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

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

Which buildkite-agent derivation to use

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).

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.

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

The token from your Buildkite "Agents" page

Add a custom host-to-IP mapping.

Select executor, eg. shell, docker, etc

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 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 is used to control whether your job is to be kept continuously running or to let demand and conditions control the invocation

Extra packages to add to PATH of the service to make them available to workflows.

Resource limits to be imposed on the job

Resource limits to be imposed on the job

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

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

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 causes the job to be started every N seconds

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

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

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

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.

Extra lines to be added verbatim to the configuration file.

Whether this file should be generated

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

This optional key is used to specify a directory to chroot(2) to before running 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

Specifies higher-level event types to be used as launch-on-demand event sources

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

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

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

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

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

This optional key is used to control whether your job is to be kept continuously running or to let demand and conditions control the invocation

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

Disables adding the default labels

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

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

The maximum size (in bytes) of the stack segment for a process; this defines how far a program's stack segment may be extended

The maximum size (in bytes) of the stack segment for a process; this defines how far a program's stack segment may be extended

Specifies higher-level event types to be used as launch-on-demand event sources

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

The public key data for the host

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

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

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

The maximum size (in bytes) of the stack segment for a process; this defines how far a program's stack segment may be extended

The maximum size (in bytes) of the stack segment for a process; this defines how far a program's stack segment may be extended

Path of the source file.

Disable all container caching.

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

Modify the service

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.

A list of additional host names and/or IP numbers used for accessing the host's ssh service

Resource limits to be imposed on the job