Skip to content

Commit

Permalink
Update help for buildkite-agent v3.59.0
Browse files Browse the repository at this point in the history
  • Loading branch information
triarius committed Nov 16, 2023
1 parent 710bc72 commit 4c37c11
Show file tree
Hide file tree
Showing 4 changed files with 102 additions and 6 deletions.
4 changes: 2 additions & 2 deletions pages/agent/v3/help/_pipeline_upload.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,8 @@ $ ./script/dynamic_step_generator | buildkite-agent pipeline upload
<tr id="format"><th><code>--format value</code> <a class="Docs__attribute__link" href="#format">#</a></th><td><p>In dry-run mode, specifies the form to output the pipeline in. Must be one of: json,yaml (default: "json")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_UPLOAD_DRY_RUN_FORMAT</code></p></td></tr>
<tr id="no-interpolation"><th><code>--no-interpolation </code> <a class="Docs__attribute__link" href="#no-interpolation">#</a></th><td><p>Skip variable interpolation into the pipeline prior to upload<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_NO_INTERPOLATION</code></p></td></tr>
<tr id="reject-secrets"><th><code>--reject-secrets </code> <a class="Docs__attribute__link" href="#reject-secrets">#</a></th><td><p>When true, fail the pipeline upload early if the pipeline contains secrets<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_PIPELINE_UPLOAD_REJECT_SECRETS</code></p></td></tr>
<tr id="jwks-file-path"><th><code>--jwks-file-path value</code> <a class="Docs__attribute__link" href="#jwks-file-path">#</a></th><td><p>EXPERIMENTAL: Path to a file containing a JWKS. Passing this flag enables pipeline signing<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_UPLOAD_JWKS_FILE_PATH</code></p></td></tr>
<tr id="signing-key-id"><th><code>--signing-key-id value</code> <a class="Docs__attribute__link" href="#signing-key-id">#</a></th><td><p>EXPERIMENTAL: The JWKS key ID to use when signing the pipeline. Required when using a JWKS<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_UPLOAD_SIGNING_KEY_ID</code></p></td></tr>
<tr id="jwks-file"><th><code>--jwks-file value</code> <a class="Docs__attribute__link" href="#jwks-file">#</a></th><td><p>EXPERIMENTAL: Path to a file containing a JWKS. Passing this flag enables pipeline signing<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JWKS_FILE</code></p></td></tr>
<tr id="jwks-key-id"><th><code>--jwks-key-id value</code> <a class="Docs__attribute__link" href="#jwks-key-id">#</a></th><td><p>EXPERIMENTAL: The JWKS key ID to use when signing the pipeline. Required when using a JWKS<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JWKS_KEY_ID</code></p></td></tr>
<tr id="agent-access-token"><th><code>--agent-access-token value</code> <a class="Docs__attribute__link" href="#agent-access-token">#</a></th><td><p>The access token used to identify the agent<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_ACCESS_TOKEN</code></p></td></tr>
<tr id="endpoint"><th><code>--endpoint value</code> <a class="Docs__attribute__link" href="#endpoint">#</a></th><td><p>The Agent API endpoint (default: "<code>https://agent.buildkite.com/v3</code>")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_ENDPOINT</code></p></td></tr>
<tr id="no-http2"><th><code>--no-http2 </code> <a class="Docs__attribute__link" href="#no-http2">#</a></th><td><p>Disable HTTP2 when communicating with the Agent API.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_NO_HTTP2</code></p></td></tr>
Expand Down
8 changes: 4 additions & 4 deletions pages/agent/v3/help/_start.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,10 +96,10 @@ $ buildkite-agent start --token xxx
<tr id="signal-grace-period-seconds"><th><code>--signal-grace-period-seconds value</code> <a class="Docs__attribute__link" href="#signal-grace-period-seconds">#</a></th><td><p>The number of seconds given to a subprocess to handle being sent `cancel-signal`. After this period has elapsed, SIGKILL will be sent. (default: 0)<br /><strong>Environment variable</strong>: <code>$BUILDKITE_SIGNAL_GRACE_PERIOD_SECONDS</code></p></td></tr>
<tr id="tracing-backend"><th><code>--tracing-backend value</code> <a class="Docs__attribute__link" href="#tracing-backend">#</a></th><td><p>Enable tracing for build jobs by specifying a backend, "datadog" or "opentelemetry"<br /><strong>Environment variable</strong>: <code>$BUILDKITE_TRACING_BACKEND</code></p></td></tr>
<tr id="tracing-service-name"><th><code>--tracing-service-name value</code> <a class="Docs__attribute__link" href="#tracing-service-name">#</a></th><td><p>Service name to use when reporting traces. (default: "buildkite-agent")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_TRACING_SERVICE_NAME</code></p></td></tr>
<tr id="job-verification-jwks-path"><th><code>--job-verification-jwks-path value</code> <a class="Docs__attribute__link" href="#job-verification-jwks-path">#</a></th><td><p>EXPERIMENTAL: Path to a file containing a JSON Web Key Set (JWKS), used to verify job signatures.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JWKS_FILE_PATH</code></p></td></tr>
<tr id="job-signing-jwks-path"><th><code>--job-signing-jwks-path value</code> <a class="Docs__attribute__link" href="#job-signing-jwks-path">#</a></th><td><p>EXPERIMENTAL: Path to a file containing a signing key. Passing this flag enables pipeline signing for all pipelines uploaded by this agent. For hmac-sha256, the raw file content is used as the shared key<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_UPLOAD_JWKS_FILE_PATH</code></p></td></tr>
<tr id="job-signing-key-id"><th><code>--job-signing-key-id value</code> <a class="Docs__attribute__link" href="#job-signing-key-id">#</a></th><td><p>EXPERIMENTAL: The JWKS key ID to use when signing the pipeline. Required when using a JWKS<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_UPLOAD_SIGNING_KEY_ID</code></p></td></tr>
<tr id="job-verification-failure-behavior"><th><code>--job-verification-failure-behavior value</code> <a class="Docs__attribute__link" href="#job-verification-failure-behavior">#</a></th><td><p>EXPERIMENTAL: The behavior when a job is received without a signature. One of: [block warn]. Defaults to block (default: "block")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JOB_VERIFICATION_NO_SIGNATURE_BEHAVIOR</code></p></td></tr>
<tr id="verification-jwks-file"><th><code>--verification-jwks-file value</code> <a class="Docs__attribute__link" href="#verification-jwks-file">#</a></th><td><p>EXPERIMENTAL: Path to a file containing a JSON Web Key Set (JWKS), used to verify job signatures.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_VERIFICATION_JWKS_FILE</code></p></td></tr>
<tr id="signing-jwks-file"><th><code>--signing-jwks-file value</code> <a class="Docs__attribute__link" href="#signing-jwks-file">#</a></th><td><p>EXPERIMENTAL: Path to a file containing a signing key. Passing this flag enables pipeline signing for all pipelines uploaded by this agent. For hmac-sha256, the raw file content is used as the shared key<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_SIGNING_JWKS_FILE</code></p></td></tr>
<tr id="signing-jwks-key-id"><th><code>--signing-jwks-key-id value</code> <a class="Docs__attribute__link" href="#signing-jwks-key-id">#</a></th><td><p>EXPERIMENTAL: The JWKS key ID to use when signing the pipeline. If ommitted, and the signing JWKS conatins only one key, that key will be used.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_SIGNING_JWKS_KEY_ID</code></p></td></tr>
<tr id="verification-failure-behavior"><th><code>--verification-failure-behavior value</code> <a class="Docs__attribute__link" href="#verification-failure-behavior">#</a></th><td><p>EXPERIMENTAL: The behavior when a job is received without a signature. One of: [block warn]. Defaults to block (default: "block")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JOB_VERIFICATION_NO_SIGNATURE_BEHAVIOR</code></p></td></tr>
<tr id="token"><th><code>--token value</code> <a class="Docs__attribute__link" href="#token">#</a></th><td><p>Your account agent token<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_TOKEN</code></p></td></tr>
<tr id="endpoint"><th><code>--endpoint value</code> <a class="Docs__attribute__link" href="#endpoint">#</a></th><td><p>The Agent API endpoint (default: "<code>https://agent.buildkite.com/v3</code>")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_ENDPOINT</code></p></td></tr>
<tr id="no-http2"><th><code>--no-http2 </code> <a class="Docs__attribute__link" href="#no-http2">#</a></th><td><p>Disable HTTP2 when communicating with the Agent API.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_NO_HTTP2</code></p></td></tr>
Expand Down
47 changes: 47 additions & 0 deletions pages/agent/v3/help/_tool_keygen.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
<!--
_____ ____ _ _ ____ _______ ______ _____ _____ _______
| __ \ / __ \ | \ | |/ __ \__ __| | ____| __ \_ _|__ __|
| | | | | | | | \| | | | | | | | |__ | | | || | | |
| | | | | | | | . ` | | | | | | | __| | | | || | | |
| |__| | |__| | | |\ | |__| | | | | |____| |__| || |_ | |
|_____/ \____/ |_| \_|\____/ |_| |______|_____/_____| |_|
This file is auto-generated by scripts/update-agent-help.sh, please update the
agent CLI help in https://github.com/buildkite/agent and run the generation
script.
-->

### Usage

`buildkite-agent tool keygen [options...]`

### Description

This (experimental!) command generates a new JWS key pair, used for signing and
verifying jobs in Buildkite.

The pair is written as a JSON Web Key Set (JWKS) to two files, a private JWKS
file and a public JWKS file. The private JWKS should be used as for signing,
and the public JWKS for verification.

For more information about JWS, see https://tools.ietf.org/html/rfc7515 and
for information about JWKS, see https://tools.ietf.org/html/rfc7517

### Options

<!-- vale off -->

<table class="Docs__attribute__table">
<tr id="alg"><th><code>--alg value</code> <a class="Docs__attribute__link" href="#alg">#</a></th><td><p>The JWS signing algorithm to use for the key pair. Valid algorithms are: [HS256 HS384 HS512 PS256 PS384 PS512 ES256 ES384 ES512 EdDSA]<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_KEYGEN_ALG</code></p></td></tr>
<tr id="key-id"><th><code>--key-id value</code> <a class="Docs__attribute__link" href="#key-id">#</a></th><td><p>The ID to use for the keys generated. If none is provided, a random one will be generated<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_KEYGEN_KEY_ID</code></p></td></tr>
<tr id="private-jwks-file"><th><code>--private-jwks-file value</code> <a class="Docs__attribute__link" href="#private-jwks-file">#</a></th><td><p>The filename to write the private key to. Defaults to a name based on the key id in the current directory<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_KEYGEN_PRIVATE_JWKS_FILE</code></p></td></tr>
<tr id="public-jwks-file"><th><code>--public-jwks-file value</code> <a class="Docs__attribute__link" href="#public-jwks-file">#</a></th><td><p>The filename to write the public keyset to. Defaults to a name based on the key id in the current directory<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_KEYGEN_PUBLIC_JWKS_FILE</code></p></td></tr>
<tr id="no-color"><th><code>--no-color </code> <a class="Docs__attribute__link" href="#no-color">#</a></th><td><p>Don't show colors in logging<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_NO_COLOR</code></p></td></tr>
<tr id="debug"><th><code>--debug </code> <a class="Docs__attribute__link" href="#debug">#</a></th><td><p>Enable debug mode. Synonym for `--log-level debug`. Takes precedence over `--log-level`<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_DEBUG</code></p></td></tr>
<tr id="log-level"><th><code>--log-level value</code> <a class="Docs__attribute__link" href="#log-level">#</a></th><td><p>Set the log level for the agent, making logging more or less verbose. Defaults to notice. Allowed values are: debug, info, error, warn, fatal (default: "notice")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_LOG_LEVEL</code></p></td></tr>
<tr id="experiment"><th><code>--experiment value</code> <a class="Docs__attribute__link" href="#experiment">#</a></th><td><p>Enable experimental features within the buildkite-agent<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_EXPERIMENT</code></p></td></tr>
<tr id="profile"><th><code>--profile value</code> <a class="Docs__attribute__link" href="#profile">#</a></th><td><p>Enable a profiling mode, either cpu, memory, mutex or block<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_PROFILE</code></p></td></tr>
</table>

<!-- vale on -->
49 changes: 49 additions & 0 deletions pages/agent/v3/help/_tool_sign.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
<!--
_____ ____ _ _ ____ _______ ______ _____ _____ _______
| __ \ / __ \ | \ | |/ __ \__ __| | ____| __ \_ _|__ __|
| | | | | | | | \| | | | | | | | |__ | | | || | | |
| | | | | | | | . ` | | | | | | | __| | | | || | | |
| |__| | |__| | | |\ | |__| | | | | |____| |__| || |_ | |
|_____/ \____/ |_| \_|\____/ |_| |______|_____/_____| |_|
This file is auto-generated by scripts/update-agent-help.sh, please update the
agent CLI help in https://github.com/buildkite/agent and run the generation
script.
-->

### Usage

`buildkite-agent tool sign-pipeline [options...] [pipeline-file]`

### Description

This (experimental!) command takes a pipeline in YAML format as input, and annotates the
appropriate parts of the pipeline with signatures. This can then be input into the YAML steps
editor in the Buildkite UI so that the agents running these steps can verify the signatures.

If a token is provided using the `graphql-token` flag, the tool will attempt to retrieve the
pipeline definition and repo using the Buildkite GraphQL API. If `update` is also set, it will
update the pipeline definition with the signed version using the GraphQL API too.

### Options

<!-- vale off -->

<table class="Docs__attribute__table">
<tr id="graphql-token"><th><code>--graphql-token value</code> <a class="Docs__attribute__link" href="#graphql-token">#</a></th><td><p>A token for the buildkite graphql API. This will be used to populate the value of the repository URL, and download the pipeline definition. Both `repo` and `pipeline-file` will be ignored in preference of values from the GraphQL API if the token in provided.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_GRAPHQL_TOKEN</code></p></td></tr>
<tr id="update"><th><code>--update </code> <a class="Docs__attribute__link" href="#update">#</a></th><td><p>Update the pipeline using the GraphQL API after signing it. This can only be used if `graphql-token` is provided.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_TOOL_SIGN_UPDATE</code></p></td></tr>
<tr id="no-confirm"><th><code>--no-confirm </code> <a class="Docs__attribute__link" href="#no-confirm">#</a></th><td><p>Show confirmation prompts before updating the pipeline with the GraphQL API.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_TOOL_SIGN_NO_CONFIRM</code></p></td></tr>
<tr id="jwks-file"><th><code>--jwks-file value</code> <a class="Docs__attribute__link" href="#jwks-file">#</a></th><td><p>Path to a file containing a JWKS.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JWKS_FILE</code></p></td></tr>
<tr id="jwks-key-id"><th><code>--jwks-key-id value</code> <a class="Docs__attribute__link" href="#jwks-key-id">#</a></th><td><p>The JWKS key ID to use when signing the pipeline. If none is provided and the JWKS file contains only one key, that key will be used.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_JWKS_KEY_ID</code></p></td></tr>
<tr id="organization-slug"><th><code>--organization-slug value</code> <a class="Docs__attribute__link" href="#organization-slug">#</a></th><td><p>The organization slug. Required to connect to the GraphQL API.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_ORGANIZATION_SLUG</code></p></td></tr>
<tr id="pipeline-slug"><th><code>--pipeline-slug value</code> <a class="Docs__attribute__link" href="#pipeline-slug">#</a></th><td><p>The pipeline slug. Required to connect to the GraphQL API.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_PIPELINE_SLUG</code></p></td></tr>
<tr id="repo"><th><code>--repo value</code> <a class="Docs__attribute__link" href="#repo">#</a></th><td><p>The URL of the pipeline's repository, which is used in the pipeline signature. If the GraphQL token is provided, this will be ignored.<br /><strong>Environment variable</strong>: <code>$BUILDKITE_REPO</code></p></td></tr>
<tr id="no-color"><th><code>--no-color </code> <a class="Docs__attribute__link" href="#no-color">#</a></th><td><p>Don't show colors in logging<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_NO_COLOR</code></p></td></tr>
<tr id="debug"><th><code>--debug </code> <a class="Docs__attribute__link" href="#debug">#</a></th><td><p>Enable debug mode. Synonym for `--log-level debug`. Takes precedence over `--log-level`<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_DEBUG</code></p></td></tr>
<tr id="log-level"><th><code>--log-level value</code> <a class="Docs__attribute__link" href="#log-level">#</a></th><td><p>Set the log level for the agent, making logging more or less verbose. Defaults to notice. Allowed values are: debug, info, error, warn, fatal (default: "notice")<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_LOG_LEVEL</code></p></td></tr>
<tr id="experiment"><th><code>--experiment value</code> <a class="Docs__attribute__link" href="#experiment">#</a></th><td><p>Enable experimental features within the buildkite-agent<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_EXPERIMENT</code></p></td></tr>
<tr id="profile"><th><code>--profile value</code> <a class="Docs__attribute__link" href="#profile">#</a></th><td><p>Enable a profiling mode, either cpu, memory, mutex or block<br /><strong>Environment variable</strong>: <code>$BUILDKITE_AGENT_PROFILE</code></p></td></tr>
</table>

<!-- vale on -->

0 comments on commit 4c37c11

Please sign in to comment.